Device, method, and graphical user interface for providing feedback for changing activation states of a user interface object

ABSTRACT

An electronic device with a touch-sensitive surface, a display, and one or more sensors to detect intensity of contacts with the touch-sensitive surface displays a user interface object having a plurality of activation states; detects a contact on the touch-sensitive surface; and detects an increase of intensity of the contact from a first intensity to a second intensity. In response to detecting the increase in intensity, the device: changes activation states M times, and generates a tactile output on the touch-sensitive surface corresponding to each change in activation state. The device detects a decrease of intensity of the contact from the second intensity to the first intensity; and in response to detecting the decrease in intensity, the device: changes activation states N times, and generates a tactile output on the touch-sensitive surface corresponding to each change in activation state, where N is different from M.

RELATED APPLICATIONS

This application is a continuation of PCT Patent Application Ser. No.PCT/US2013/040072, filed on May 8, 2013, entitled “Device, Method, andGraphical User Interface for Providing Feedback for Changing ActivationStates of a User Interface Object,” which claims the benefit of andpriority to U.S. Provisional Patent Application Ser. No. 61/778,287,filed on Mar. 12, 2013, entitled “Device, Method, and Graphical UserInterface for Providing Feedback for Changing Activation States of aUser Interface Object;” U.S. Provisional Patent Application No.61/747,278, filed Dec. 29, 2012, entitled “Device, Method, and GraphicalUser Interface for Manipulating User Interface Objects with Visualand/or Haptic Feedback;” and U.S. Provisional Patent Application No.61/688,227, filed May 9, 2012, entitled “Device, Method, and GraphicalUser Interface for Manipulating User Interface Objects with Visualand/or Haptic Feedback,” which applications are incorporated byreference herein in their entireties.

This application is also related to the following: U.S. ProvisionalPatent Application Ser. No. 61/778,092, filed on Mar. 12, 2013, entitled“Device, Method, and Graphical User Interface for Selecting Objectwithin a Group of Objects;” U.S. Provisional Patent Application Ser. No.61/778,125, filed on Mar. 12, 2013, entitled “Device, Method, andGraphical User Interface for Navigating User Interface Hierarchies;”U.S. Provisional Patent Application Ser. No. 61/778,156, filed on Mar.12, 2013, entitled “Device, Method, and Graphical User Interface forManipulating Framed Graphical Objects;” U.S. Provisional PatentApplication Ser. No. 61/778,179, filed on Mar. 12, 2013, entitled“Device, Method, and Graphical User Interface for Scrolling NestedRegions;” U.S. Provisional Patent Application Ser. No. 61/778,171, filedon Mar. 12, 2013, entitled “Device, Method, and Graphical User Interfacefor Displaying Additional Information in Response to a User Contact;”U.S. Provisional Patent Application Ser. No. 61/778,191, filed on Mar.12, 2013, entitled “Device, Method, and Graphical User Interface forDisplaying User Interface Objects Corresponding to an Application;” U.S.Provisional Patent Application Ser. No. 61/778,211, filed on Mar. 12,2013, entitled “Device, Method, and Graphical User Interface forFacilitating User Interaction with Controls in a User Interface;” U.S.Provisional Patent Application Ser. No. 61/778,239, filed on Mar. 12,2013, entitled “Device, Method, and Graphical User Interface forForgoing Generation of Tactile Output for a Multi-Contact Gesture;” U.S.Provisional Patent Application Ser. No. 61/778,284, filed on Mar. 12,2013, entitled “Device, Method, and Graphical User Interface forProviding Tactile Feedback for Operations Performed in a UserInterface;” U.S. Provisional Patent Application Ser. No. 61/778,363,filed on Mar. 12, 2013, entitled “Device, Method, and Graphical UserInterface for Transitioning between Touch Input to Display OutputRelationships;” U.S. Provisional Patent Application Ser. No. 61/778,367,filed on Mar. 12, 2013, entitled “Device, Method, and Graphical UserInterface for Moving a User Interface Object Based on an Intensity of aPress Input;” U.S. Provisional Patent Application Ser. No. 61/778,265,filed on Mar. 12, 2013, entitled “Device, Method, and Graphical UserInterface for Transitioning between Display States in Response to aGesture;” U.S. Provisional Patent Application Ser. No. 61/778,373, filedon Mar. 12, 2013, entitled “Device, Method, and Graphical User Interfacefor Managing Activation of a Control Based on Contact Intensity;” U.S.Provisional Patent Application Ser. No. 61/778,412, filed on Mar. 13,2013, entitled “Device, Method, and Graphical User Interface forDisplaying Content Associated with a Corresponding Affordance;” U.S.Provisional Patent Application Ser. No. 61/778,413, filed on Mar. 13,2013, entitled “Device, Method, and Graphical User Interface forSelecting User Interface Objects;” U.S. Provisional Patent ApplicationSer. No. 61/778,414, filed on Mar. 13, 2013, entitled “Device, Method,and Graphical User Interface for Moving and Dropping a User InterfaceObject;” U.S. Provisional Patent Application Ser. No. 61/778,416, filedon Mar. 13, 2013, entitled “Device, Method, and Graphical User Interfacefor Determining Whether to Scroll or Select Content;” and U.S.Provisional Patent Application Ser. No. 61/778,418, filed on Mar. 13,2013, entitled “Device, Method, and Graphical User Interface forSwitching between User Interfaces,” which are incorporated herein byreference in their entireties.

This application is also related to the following: U.S. ProvisionalPatent Application Ser. No. 61/645,033, filed on May 9, 2012, entitled“Adaptive Haptic Feedback for Electronic Devices;” U.S. ProvisionalPatent Application Ser. No. 61/665,603, filed on Jun. 28, 2012, entitled“Adaptive Haptic Feedback for Electronic Devices;” and U.S. ProvisionalPatent Application Ser. No. 61/681,098, filed on Aug. 8, 2012, entitled“Adaptive Haptic Feedback for Electronic Devices,” which areincorporated herein by reference in their entireties.

TECHNICAL FIELD

This relates generally to electronic devices with touch-sensitivesurfaces, including but not limited to electronic devices withtouch-sensitive surfaces that detect inputs for manipulating userinterfaces.

BACKGROUND

The use of touch-sensitive surfaces as input devices for computers andother electronic computing devices has increased significantly in recentyears. Exemplary touch-sensitive surfaces include touch pads and touchscreen displays. Such surfaces are widely used to manipulate userinterface objects on a display.

Exemplary manipulations include adjusting the position and/or size ofone or more user interface objects or activating buttons or openingfiles/applications represented by user interface objects, as well asassociating metadata with one or more user interface objects orotherwise manipulating user interfaces. Exemplary user interface objectsinclude digital images, video, text, icons, control elements such asbuttons and other graphics. A user will, in some circumstances, need toperform such manipulations on user interface objects in a filemanagement program (e.g., Finder from Apple Inc. of Cupertino, Calif.),an image management application (e.g., Aperture or iPhoto from AppleInc. of Cupertino, Calif.), a digital content (e.g., videos and music)management application (e.g., iTunes from Apple Inc. of Cupertino,Calif.), a drawing application, a presentation application (e.g.,Keynote from Apple Inc. of Cupertino, Calif.), a word processingapplication (e.g., Pages from Apple Inc. of Cupertino, Calif.), awebsite creation application (e.g., iWeb from Apple Inc. of Cupertino,Calif.), a disk authoring application (e.g., iDVD from Apple Inc. ofCupertino, Calif.), or a spreadsheet application (e.g., Numbers fromApple Inc. of Cupertino, Calif.).

But existing methods for performing these manipulations are cumbersomeand inefficient. In addition, existing methods take longer thannecessary, thereby wasting energy. This latter consideration isparticularly important in battery-operated devices.

SUMMARY

Accordingly, there is a need for electronic devices with faster, moreefficient methods and interfaces for manipulating user interfaces. Suchmethods and interfaces optionally complement or replace conventionalmethods for manipulating user interfaces. Such methods and interfacesreduce the cognitive burden on a user and produce a more efficienthuman-machine interface. For battery-operated devices, such methods andinterfaces conserve power and increase the time between battery charges.

The above deficiencies and other problems associated with userinterfaces for electronic devices with touch-sensitive surfaces arereduced or eliminated by the disclosed devices. In some embodiments, thedevice is a desktop computer. In some embodiments, the device isportable (e.g., a notebook computer, tablet computer, or handhelddevice). In some embodiments, the device has a touchpad. In someembodiments, the device has a touch-sensitive display (also known as a“touch screen” or “touch screen display”). In some embodiments, thedevice has a graphical user interface (GUI), one or more processors,memory and one or more modules, programs or sets of instructions storedin the memory for performing multiple functions. In some embodiments,the user interacts with the GUI primarily through finger contacts andgestures on the touch-sensitive surface. In some embodiments, thefunctions optionally include image editing, drawing, presenting, wordprocessing, website creating, disk authoring, spreadsheet making, gameplaying, telephoning, video conferencing, e-mailing, instant messaging,workout support, digital photographing, digital videoing, web browsing,digital music playing, and/or digital video playing. Executableinstructions for performing these functions are, optionally, included ina non-transitory computer readable storage medium or other computerprogram product configured for execution by one or more processors.

There is a need for electronic devices with faster, more efficientmethods and interfaces for selecting a tactile output corresponding to achange in intensity of a contact when relocating user interface objects.Such methods and interfaces may complement or replace conventionalmethods for relocating user interface objects. Such methods andinterfaces reduce the cognitive burden on a user and produce a moreefficient human-machine interface. For battery-operated devices, suchmethods and interfaces conserve power and increase the time betweenbattery charges.

The above deficiencies and other problems associated with userinterfaces for electronic devices with touch-sensitive surfaces arereduced or eliminated by the disclosed devices. In some embodiments, thedevice is a desktop computer. In some embodiments, the device isportable (e.g., a notebook computer, tablet computer, or handhelddevice). In some embodiments, the device has a touchpad. In someembodiments, the device has a touch-sensitive display (also known as a“touch screen” or “touch screen display”). In some embodiments, thedevice has a graphical user interface (GUI), one or more processors,memory and one or more modules, programs or sets of instructions storedin the memory for performing multiple functions. In some embodiments,the user interacts with the GUI primarily through finger contacts andgestures on the touch-sensitive surface. In some embodiments, thefunctions may include image editing, drawing, presenting, wordprocessing, website creating, disk authoring, spreadsheet making, gameplaying, telephoning, video conferencing, e-mailing, instant messaging,workout support, digital photographing, digital videoing, web browsing,digital music playing, and/or digital video playing. Executableinstructions for performing these functions may be included in anon-transitory computer readable storage medium or other computerprogram product configured for execution by one or more processors.

In accordance with some embodiments, a method is performed at anelectronic device with a touch-sensitive surface and a display, wherethe device includes one or more sensors to detect intensity of contactswith the touch-sensitive surface. The method includes: displaying a userinterface object on the display; detecting, on the touch-sensitivesurface, a contact having an intensity above an object-selectionthreshold; detecting movement of the contact across the touch-sensitivesurface, the movement corresponding to a preliminary portion of agesture for performing an operation corresponding to the user interfaceobject; detecting a reduction in intensity of the contact below anobject-release threshold; and in response to detecting the reduction inintensity below the object-release threshold: in accordance with adetermination that the movement meets predefined operation-performancecriteria: performing the operation and generating a first tactile outputon the touch-sensitive surface; and in accordance with a determinationthat the movement does not meet the predefined operation-performancecriteria: forgoing performance of the operation and generating a secondtactile output on the touch-sensitive surface, where the second tactileoutput is different from the first tactile output.

In accordance with some embodiments, an electronic device comprises adisplay unit configured to display a user interface object; atouch-sensitive surface unit configured to receive contacts; one or moresensor units configured to detect intensity of contacts with thetouch-sensitive surface unit; and a processing unit coupled to thedisplay unit, the touch-sensitive surface unit, and the sensor units.The processing unit is configured to: detect, on the touch-sensitivesurface unit, a contact having an intensity above an object-selectionthreshold; detect movement of the contact across the touch-sensitivesurface unit, the movement corresponding to a preliminary portion of agesture for performing an operation corresponding to the user interfaceobject; detect a reduction in intensity of the contact below anobject-release threshold; and in response to detecting the reduction inintensity below the object-release threshold: in accordance with adetermination that the movement meets predefined operation-performancecriteria: perform the operation; and generate a first tactile output onthe touch-sensitive surface unit; and in accordance with a determinationthat the movement does not meet the predefined operation-performancecriteria: forgo performance of the operation; and generate a secondtactile output on the touch-sensitive surface unit, wherein the secondtactile output is different from the first tactile output.

Thus, electronic devices with displays, touch-sensitive surfaces, andone or more sensors to detect intensity of contacts with thetouch-sensitive surfaces are provided with faster, more efficientmethods and interfaces for selecting a tactile output corresponding to achange in intensity of a contact when relocating user interface objects,thereby increasing the effectiveness, efficiency, and user satisfactionwith such devices. Such methods and interfaces optionally complement orreplace conventional methods for dragging and dropping user interfaceobjects.

There is a need for electronic devices with faster, more efficientmethods and interfaces for providing feedback corresponding to modifierinputs. Such methods and interfaces may complement or replaceconventional methods for providing feedback corresponding to modifierinputs. Such methods and interfaces reduce the cognitive burden on auser and produce a more efficient human-machine interface. Forbattery-operated devices, such methods and interfaces conserve power andincrease the time between battery charges.

In accordance with some embodiments, a method is performed at anelectronic device with a display, a touch-sensitive surface and one ormore sensors to detect intensity of contacts with the touch-sensitivesurface. The method includes: detecting a contact on the touch-sensitivesurface; detecting an increase in intensity of the contact above a firstactivation threshold; after detecting the increase in intensity of thecontact above the first activation threshold, detecting a reduction inintensity of the contact below a second activation threshold; and inresponse to detecting the reduction in intensity of the contact belowthe second activation threshold: in accordance with a determination thata modifier input was detected while detecting the increase in intensityof the contact above the first activation threshold: performing a firstoperation and generating a first tactile output on the touch-sensitivesurface; and in accordance with a determination that the modifier inputwas not detected while detecting the increase in intensity of thecontact above the first activation threshold: performing a secondoperation different from the first operation and generating a secondtactile output on the touch-sensitive surface, where the second tactileoutput is different from the first tactile output.

In accordance with some embodiments, an electronic device includes adisplay unit; a touch-sensitive surface unit configured to receivecontacts; one or more sensor units configured to detect intensity ofcontacts with the touch-sensitive surface unit; and a processing unitcoupled to the display unit, the touch-sensitive surface unit and thesensor units. The processing unit is configured to: detect a contact onthe touch-sensitive surface unit; detect an increase in intensity of thecontact above a first activation threshold; after detecting the increasein intensity of the contact above the first activation threshold, detecta reduction in intensity of the contact below a second activationthreshold; and in response to detecting the reduction in intensity ofthe contact below the second activation threshold: in accordance with adetermination that a modifier input was detected while detecting theincrease in intensity of the contact above the first activationthreshold: perform a first operation and generate a first tactile outputon the touch-sensitive surface unit; and in accordance with adetermination that the modifier input was not detected while detectingthe increase in intensity of the contact above the first activationthreshold: perform a second operation different from the first operationand generate a second tactile output on the touch-sensitive surfaceunit, where the second tactile output is different from the firsttactile output.

Thus, electronic devices with displays, touch-sensitive surfaces and oneor more sensors to detect intensity of contacts with the touch-sensitivesurfaces are provided with faster, more efficient methods and interfacesfor providing feedback corresponding to modifier inputs, therebyincreasing the effectiveness, efficiency, and user satisfaction withsuch devices. Such methods and interfaces may complement or replaceconventional methods for providing feedback corresponding to modifierinputs.

There is a need for electronic devices with more efficient methods andinterfaces for providing feedback for changing activation states of auser interface object. Such methods and interfaces may complement orreplace conventional methods for providing feedback for changingactivation states of a user interface object. Such methods andinterfaces reduce the cognitive burden on a user and produce a moreefficient human-machine interface. For battery-operated devices, suchmethods and interfaces conserve power and increase the time betweenbattery charges.

In accordance with some embodiments, a method is performed at anelectronic device with a display, a touch-sensitive surface and one ormore sensors to detect intensity of contacts with the touch-sensitivesurface. The method includes: displaying a user interface object on thedisplay, where the user interface object has a plurality of activationstates; detecting a contact on the touch-sensitive surface; detecting anincrease of intensity of the contact on the touch-sensitive surface froma first intensity to a second intensity; in response to detecting theincrease in intensity: changing activation states of the user interfaceobject M times, where M is a positive integer, and generating a tactileoutput on the touch-sensitive surface corresponding to each change inactivation state of the user interface object; detecting a decrease ofintensity of the contact from the second intensity to the firstintensity; and in response to detecting the decrease in intensity:changing activation states of the user interface object N times, where Nis a positive integer, and generating a tactile output on thetouch-sensitive surface corresponding to each change in activation stateof the user interface object, where N is different from M.

In accordance with some embodiments, an electronic device includes adisplay unit configured to display a user interface object, where theuser interface object has a plurality of activation states, atouch-sensitive surface unit configured to receive contacts, one or moresensor units configured to detect intensity of contacts with thetouch-sensitive surface unit, and a processing unit coupled to thedisplay unit, the touch-sensitive surface unit, and the sensor units.The processing unit is configured to: detect a contact on thetouch-sensitive surface unit; detect an increase of intensity of thecontact on the touch-sensitive surface unit from a first intensity to asecond intensity; in response to detecting the increase in intensity:change activation states of the user interface object M times, where Mis a positive integer, and generate a tactile output on thetouch-sensitive surface unit corresponding to each change in activationstate of the user interface object; detect a decrease of intensity ofthe contact from the second intensity to the first intensity; and inresponse to detecting the decrease in intensity: change activationstates of the user interface object N times, where N is a positiveinteger, and generate a tactile output on the touch-sensitive surfaceunit corresponding to each change in activation state of the userinterface object, where N is different from M.

Thus, electronic devices with displays, touch-sensitive surfaces and oneor more sensors to detect intensity of contacts with the touch-sensitivesurface are provided with more efficient methods and interfaces forproviding feedback for changing activation states of a user interfaceobject, thereby increasing the effectiveness, efficiency, and usersatisfaction with such devices. Such methods and interfaces maycomplement or replace conventional methods for providing feedback forchanging activation states of a user interface object.

There is a need for electronic devices with faster, more efficientmethods and interfaces for providing feedback for changing activationstates of a user interface object. Such methods and interfaces maycomplement or replace conventional methods for providing feedback forchanging activation states of a user interface object. Such methods andinterfaces reduce the cognitive burden on a user and produce a moreefficient human-machine interface. For battery-operated devices, suchmethods and interfaces conserve power and increase the time betweenbattery charges.

In accordance with some embodiments, a method is performed at anelectronic device with a display, a touch-sensitive surface and one ormore sensors to detect intensity of contacts with the touch-sensitivesurface. The method includes: displaying a user interface object on thedisplay, where the user interface object has a first activation stateand a second activation state; detecting a contact on thetouch-sensitive surface; detecting an increase of intensity of thecontact on the touch-sensitive surface from a first intensity to asecond intensity; in response to detecting the increase in intensity:changing activation states of the user interface object from the firstactivation state to the second activation state; and generating Mdistinct tactile outputs on the touch-sensitive surface, where M is apositive integer; detecting a decrease of intensity of the contact fromthe second intensity to the first intensity; and in response todetecting the decrease in intensity: changing activation states of theuser interface object from the second activation state to the firstactivation state; and generating N distinct tactile outputs on thetouch-sensitive surface, where N is a positive integer and N isdifferent from M.

In accordance with some embodiments, an electronic device includes adisplay unit configured to display a user interface object, where theuser interface object has a first activation state and a secondactivation state; a touch-sensitive surface unit configured to receivecontacts; one or more sensor units configured to detect intensity ofcontacts with the touch-sensitive surface unit; and a processing unitcoupled to the display unit, the touch-sensitive surface unit and thesensor units. The processing unit is configured to: detect a contact onthe touch-sensitive surface unit; detect an increase of intensity of thecontact on the touch-sensitive surface unit from a first intensity to asecond intensity; in response to detecting the increase in intensity:change activation states of the user interface object from the firstactivation state to the second activation state; and generate M distincttactile outputs on the touch-sensitive surface unit, where M is apositive integer; detect a decrease of intensity of the contact from thesecond intensity to the first intensity; and in response to detectingthe decrease in intensity: change activation states of the userinterface object from the second activation state to the firstactivation state; and generate N distinct tactile outputs on thetouch-sensitive surface unit, where N is a positive integer and N isdifferent from M.

Thus, electronic devices with displays, touch-sensitive surfaces and oneor more sensors to detect intensity of contacts with the touch-sensitivesurface are provided with faster, more efficient methods and interfacesfor providing feedback for changing activation states of a userinterface object, thereby increasing the effectiveness, efficiency, anduser satisfaction with such devices. Such methods and interfaces maycomplement or replace conventional methods for providing feedback forchanging activation states of a user interface object.

In accordance with some embodiments, an electronic device includes adisplay, a touch-sensitive surface, optionally one or more sensors todetect intensity of contacts with the touch-sensitive surface, one ormore processors, memory, and one or more programs; the one or moreprograms are stored in the memory and configured to be executed by theone or more processors and the one or more programs include instructionsfor performing the operations of any of the methods referred to in thefifth paragraph of the Description of Embodiments. In accordance withsome embodiments, a graphical user interface on an electronic devicewith a display, a touch-sensitive surface, optionally one or moresensors to detect intensity of contacts with the touch-sensitivesurface, a memory, and one or more processors to execute one or moreprograms stored in the memory includes one or more of the elementsdisplayed in any of the methods referred to in the fifth paragraph ofthe Description of Embodiments, which are updated in response to inputs,as described in any of the methods referred to in the fifth paragraph ofthe Description of Embodiments. In accordance with some embodiments, acomputer readable storage medium has stored therein instructions whichwhen executed by an electronic device with a display, a touch-sensitivesurface, and optionally one or more sensors to detect intensity ofcontacts with the touch-sensitive surface, cause the device to performthe operations of any of the methods referred to in the fifth paragraphof the Description of Embodiments. In accordance with some embodiments,an electronic device includes: a display, a touch-sensitive surface, andoptionally one or more sensors to detect intensity of contacts with thetouch-sensitive surface; and means for performing the operations of anyof the methods referred to in the fifth paragraph of the Description ofEmbodiments. In accordance with some embodiments, an informationprocessing apparatus, for use in an electronic device with a display anda touch-sensitive surface, optionally one or more sensors to detectintensity of contacts with the touch-sensitive surface, includes meansfor performing the operations of any of the methods referred to in thefifth paragraph of the Description of Embodiments.

BRIEF DESCRIPTION OF THE DRAWINGS

For a better understanding of the various described embodiments,reference should be made to the Description of Embodiments below, inconjunction with the following drawings in which like reference numeralsrefer to corresponding parts throughout the figures.

FIG. 1A is a block diagram illustrating a portable multifunction devicewith a touch-sensitive display in accordance with some embodiments.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments.

FIG. 2 illustrates a portable multifunction device having a touch screenin accordance with some embodiments.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on a portable multifunction device in accordance with someembodiments.

FIG. 4B illustrates an exemplary user interface for a multifunctiondevice with a touch-sensitive surface that is separate from the displayin accordance with some embodiments.

FIGS. 5A-5W illustrate exemplary user interfaces for selecting a tactileoutput corresponding to a change in intensity of a contact in accordancewith some embodiments.

FIGS. 6A-6B are flow diagrams illustrating a method of selecting atactile output corresponding to a change in intensity of a contact inaccordance with some embodiments.

FIG. 7 is a functional block diagram of an electronic device inaccordance with some embodiments.

FIGS. 8A-8V illustrate exemplary user interfaces for providing feedbackcorresponding to modifier inputs in accordance with some embodiments.

FIGS. 9A-9B are flow diagrams illustrating a method of providingfeedback corresponding to modifier inputs in accordance with someembodiments.

FIG. 10 is a functional block diagram of an electronic device inaccordance with some embodiments.

FIGS. 11A-11N illustrate exemplary user interfaces for providingfeedback for changing activation states of a user interface object inaccordance with some embodiments.

FIGS. 12A-12B are flow diagrams illustrating a method of providingfeedback for changing activation states of a user interface object inaccordance with some embodiments.

FIG. 13 is a functional block diagram of an electronic device inaccordance with some embodiments.

FIGS. 14A-14N illustrate exemplary user interfaces for providingfeedback for changing activation states of a user interface object inaccordance with some embodiments.

FIGS. 15A-15C are flow diagrams illustrating a method of providingfeedback for changing activation states of a user interface object inaccordance with some embodiments.

FIG. 16 is a functional block diagram of an electronic device inaccordance with some embodiments.

DESCRIPTION OF EMBODIMENTS

The methods, devices and GUIs described herein provide visual and/orhaptic feedback that makes manipulation of user interface objects moreefficient and intuitive for a user. For example, in a system where theclicking action of a trackpad is decoupled from the contact intensity(e.g., contact force, contact pressure, or a substitute therefore) thatis needed to reach an activation threshold, the device can generatedifferent tactile outputs (e.g., “different clicks”) for differentactivation events (e.g., so that clicks that accomplish a particularresult are differentiated from clicks that do not produce any result orthat accomplish a different result from the particular result).Additionally, tactile outputs can be generated in response to otherevents that are not related to increasing intensity of a contact, suchas generating a tactile output (e.g., a “detent”) when a user interfaceobject is moved to a particular position, boundary or orientation, orwhen an event occurs at the device.

Additionally, in a system where a trackpad or touch-screen display issensitive to a range of contact intensity that includes more than one ortwo specific intensity values (e.g., more than a simple on/off, binaryintensity determination), the user interface can provide responses(e.g., visual or tactile cues) that are indicative of the intensity ofthe contact within the range. In some implementations, apre-activation-threshold response and/or a post-activation-thresholdresponse to an input are displayed as continuous animations. As oneexample of such a response, a preview of an operation is displayed inresponse to detecting an increase in contact intensity that is stillbelow an activation threshold for performing the operation. As anotherexample of such a response, an animation associated with an operationcontinues even after the activation threshold for the operation has beenreached. Both of these examples provide a user with a continuousresponse to the force or pressure of a user's contact, which provides auser with visual and/or haptic feedback that is richer and moreintuitive. More specifically, such continuous force responses give theuser the experience of being able to press lightly to preview anoperation and/or press deeply to push “past” or “through” a predefineduser interface state corresponding to the operation.

Additionally, for a device with a touch-sensitive surface that issensitive to a range of contact intensity, multiple contact intensitythresholds can be monitored by the device and different functions can bemapped to different contact intensity thresholds. This serves toincrease the available “gesture space” providing easy access to advancedfeatures for users who know that increasing the intensity of a contactat or beyond a second “deep press” intensity threshold will cause thedevice to perform a different operation from an operation that would beperformed if the intensity of the contact is between a first“activation” intensity threshold and the second “deep press” intensitythreshold. An advantage of assigning additional functionality to asecond “deep press” intensity threshold while maintaining familiarfunctionality at a first “activation” intensity threshold is thatinexperienced users who are, in some circumstances, confused by theadditional functionality can use the familiar functionality by justapplying an intensity up to the first “activation” intensity threshold,whereas more experienced users can take advantage of the additionalfunctionality by applying an intensity at the second “deep press”intensity threshold.

Additionally, for a device with a touch-sensitive surface that issensitive to a range of contact intensity, the device can provideadditional functionality by allowing users to perform complex operationswith a single continuous contact. For example, when selecting a group ofobjects, a user can move a continuous contact around the touch-sensitivesurface and can press while dragging (e.g., applying an intensitygreater than a “deep press” intensity threshold) to add additionalelements to a selection. In this way, a user can intuitively interactwith a user interface where pressing harder with a contact causesobjects in the user interface to be “stickier.”

A number of different approaches to providing an intuitive userinterface on a device where a clicking action is decoupled from theforce that is needed to reach an activation threshold and/or the deviceis sensitive to a wide range of contact intensities are described below.Using one or more of these approaches (optionally in conjunction witheach other) helps to provide a user interface that intuitively providesusers with additional information and functionality, thereby reducingthe user's cognitive burden and improving the human-machine interface.Such improvements in the human-machine interface enable users to use thedevice faster and more efficiently. For battery-operated devices, theseimprovements conserve power and increase the time between batterycharges. For ease of explanation, systems, methods and user interfacesfor including illustrative examples of some of these approaches aredescribed below, as follows:

-   -   Many electronic devices have graphical user interfaces including        one or more user interface objects. When users attempt to        perform operations associated with these user interface objects,        these operations are sometimes successful and sometimes        unsuccessful. For example, in some circumstances, moving a user        interface object to a disallowed portion of the user interface        will be unsuccessful, whereas moving the same user interface        object to an allowed portion of the user interface will be        successful. One approach to indicating whether an operation was        successful or unsuccessful is providing visual feedback        indicative of the successful performance of an operation.        However, visual feedback can easily be missed by a user, thereby        leaving the user confused as to whether or not the operation has        been performed. The embodiments described below improve on these        methods by providing additional cues to the user, including        tactile outputs, to indicate whether or not an operation was        successful, thereby providing a more convenient and efficient        user interface. In particular, FIGS. 5A-5W illustrate exemplary        user interfaces for relocating a user interface object in        accordance with some embodiments. FIGS. 6A-6B are flow diagrams        illustrating a method of selecting a tactile output        corresponding to a change in intensity of a contact in        accordance with some embodiments. The user interfaces in FIGS.        5A-5W are used to illustrate the processes described below,        including the processes in FIGS. 6A-6B.    -   Many electronic devices include a mouse or similar input device        that provides left-click functionality and right-click        functionality for activating different operations. As devices        economize on the number of buttons and input devices, the        left-click functionality and right-click functionality is,        optionally, invoked using one input device, such as a trackpad.        In some methods, when either functionality is invoked using the        one input device, the user is not given sufficient feedback        indicating whether the activated operation was an operation not        associated with a modifier input (e.g., a left-click operation)        or an operation associated with a modifier input (e.g., a        right-click operation). The embodiments below improve on the        these methods by providing different tactile output when device        detects an input while a modifier input is detected than when        the device detects a similar input while a modifier input is not        detected, thereby providing a more convenient and efficient user        interface. In particular, FIGS. 8A-8V illustrate exemplary user        interfaces for providing feedback corresponding to modifier        inputs. FIGS. 9A-9B are flow diagrams illustrating a method of        providing feedback corresponding to modifier inputs. The user        interfaces in FIGS. 8A-8V are used to illustrate the processes        in FIGS. 9A-9B.    -   Many electronic devices have graphical user interfaces that        include user interface objects, such as virtual buttons and        switches. In some circumstances, a user activates a user        interface object to perform an operation or adjust a parameter        or property. One approach to indicating an activation state of a        user interface object is to mimic the behavior of a        corresponding physical object. However, physical objects, such        as real buttons and switches, will, in some circumstances        provide excessive tactile feedback in some circumstances, and        too little feedback in others. The embodiments described below        provide tactile feedback that corresponds to changes in        activation states of a virtual button, switch or other user        interface object rather than tactile feedback that corresponds        1:1 to tactile sensations that would be felt by a user when        using a physical control to perform similar operations, thereby        providing a more convenient and intuitive user interface. In        particular, FIGS. 11A-11N illustrate exemplary user interfaces        for providing feedback for changing activation states of a user        interface object. FIGS. 12A-12B are flow diagrams illustrating a        method of providing feedback for changing activation states of a        user interface object. The user interfaces in FIGS. 11A-11N are        used to illustrate the processes in FIGS. 12A-12B.    -   Many electronic devices have graphical user interfaces that        include user interface objects, such as buttons and switches. In        some circumstances, a user activates a user interface object to        perform an operation or adjust a parameter or property. One        approach to indicating an activation state of a user interface        object is to mimic the behavior of a corresponding physical        object. However, physical objects, such as real buttons and        switches, will, in some circumstances provide excessive tactile        feedback in some circumstances, and too little feedback in        others. In some devices, a tactile sensation is, in some        circumstances, perceived by the user for corresponding physical        inputs, such as clicks of a physical actuator mechanism (e.g., a        mouse button) that activate a switch. The embodiments described        below provide tactile feedback that is not tied to actuations of        a physical actuator mechanism. For example, tactile sensations        related to activation state changes are, optionally, provided.        When tactile sensations not tied to physical actuations are        provided for, the user can better discern the activation state        of the virtual button without being distracted by too much or        too little tactile feedback, thereby providing a more convenient        and intuitive user interface. Below, FIGS. 14A-14N illustrate        exemplary user interfaces for providing feedback for changing        activation states of a user interface object. FIGS. 15A-15C are        flow diagrams illustrating a method of providing feedback for        changing activation states of a user interface object. The user        interfaces in FIGS. 14A-14N are used to illustrate the processes        in FIGS. 15A-15C.

Exemplary Devices

Reference will now be made in detail to embodiments, examples of whichare illustrated in the accompanying drawings. In the following detaileddescription, numerous specific details are set forth in order to providea thorough understanding of the various described embodiments. However,it will be apparent to one of ordinary skill in the art that the variousdescribed embodiments may be practiced without these specific details.In other instances, well-known methods, procedures, components,circuits, and networks have not been described in detail so as not tounnecessarily obscure aspects of the embodiments.

It will also be understood that, although the terms first, second, etc.are, in some instances, used herein to describe various elements, theseelements should not be limited by these terms. These terms are only usedto distinguish one element from another. For example, a first contactcould be termed a second contact, and, similarly, a second contact couldbe termed a first contact, without departing from the scope of thevarious described embodiments. The first contact and the second contactare both contacts, but they are not the same contact.

The terminology used in the description of the various describedembodiments herein is for the purpose of describing particularembodiments only and is not intended to be limiting. As used in thedescription of the various described embodiments and the appendedclaims, the singular forms “a”, “an” and “the” are intended to includethe plural forms as well, unless the context clearly indicatesotherwise. It will also be understood that the term “and/or” as usedherein refers to and encompasses any and all possible combinations ofone or more of the associated listed items. It will be furtherunderstood that the terms “includes,” “including,” “comprises,” and/or“comprising,” when used in this specification, specify the presence ofstated features, integers, steps, operations, elements, and/orcomponents, but do not preclude the presence or addition of one or moreother features, integers, steps, operations, elements, components,and/or groups thereof.

As used herein, the term “if” is, optionally, construed to mean “when”or “upon” or “in response to determining” or “in response to detecting,”depending on the context. Similarly, the phrase “if it is determined” or“if [a stated condition or event] is detected” is, optionally, construedto mean “upon determining” or “in response to determining” or “upondetecting [the stated condition or event]” or “in response to detecting[the stated condition or event],” depending on the context.

Embodiments of electronic devices, user interfaces for such devices, andassociated processes for using such devices are described. In someembodiments, the device is a portable communications device, such as amobile telephone, that also contains other functions, such as PDA and/ormusic player functions. Exemplary embodiments of portable multifunctiondevices include, without limitation, the iPhone®, iPod Touch®, and iPad®devices from Apple Inc. of Cupertino, Calif. Other portable electronicdevices, such as laptops or tablet computers with touch-sensitivesurfaces (e.g., touch screen displays and/or touch pads), are,optionally, used. It should also be understood that, in someembodiments, the device is not a portable communications device, but isa desktop computer with a touch-sensitive surface (e.g., a touch screendisplay and/or a touch pad).

In the discussion that follows, an electronic device that includes adisplay and a touch-sensitive surface is described. It should beunderstood, however, that the electronic device optionally includes oneor more other physical user-interface devices, such as a physicalkeyboard, a mouse and/or a joystick.

The device typically supports a variety of applications, such as one ormore of the following: a drawing application, a presentationapplication, a word processing application, a website creationapplication, a disk authoring application, a spreadsheet application, agaming application, a telephone application, a video conferencingapplication, an e-mail application, an instant messaging application, aworkout support application, a photo management application, a digitalcamera application, a digital video camera application, a web browsingapplication, a digital music player application, and/or a digital videoplayer application.

The various applications that are executed on the device optionally useat least one common physical user-interface device, such as thetouch-sensitive surface. One or more functions of the touch-sensitivesurface as well as corresponding information displayed on the deviceare, optionally, adjusted and/or varied from one application to the nextand/or within a respective application. In this way, a common physicalarchitecture (such as the touch-sensitive surface) of the deviceoptionally supports the variety of applications with user interfacesthat are intuitive and transparent to the user.

Attention is now directed toward embodiments of portable devices withtouch-sensitive displays. FIG. 1A is a block diagram illustratingportable multifunction device 100 with touch-sensitive displays 112 inaccordance with some embodiments. Touch-sensitive display 112 issometimes called a “touch screen” for convenience, and is sometimesknown as or called a touch-sensitive display system. Device 100 includesmemory 102 (which optionally includes one or more computer readablestorage mediums), memory controller 122, one or more processing units(CPU's) 120, peripherals interface 118, RF circuitry 108, audiocircuitry 110, speaker 111, microphone 113, input/output (I/O) subsystem106, other input or control devices 116, and external port 124. Device100 optionally includes one or more optical sensors 164. Device 100optionally includes one or more intensity sensors 165 for detectingintensity of contacts on device 100 (e.g., a touch-sensitive surfacesuch as touch-sensitive display system 112 of device 100). Device 100optionally includes one or more tactile output generators 167 forgenerating tactile outputs on device 100 (e.g., generating tactileoutputs on a touch-sensitive surface such as touch-sensitive displaysystem 112 of device 100 or touchpad 355 of device 300). Thesecomponents optionally communicate over one or more communication busesor signal lines 103.

As used in the specification and claims, the term “intensity” of acontact on a touch-sensitive surface refers to the force or pressure(force per unit area) of a contact (e.g., a finger contact) on the touchsensitive surface, or to a substitute (proxy) for the force or pressureof a contact on the touch sensitive surface. The intensity of a contacthas a range of values that includes at least four distinct values andmore typically includes hundreds of distinct values (e.g., at least256). Intensity of a contact is, optionally, determined (or measured)using various approaches and various sensors or combinations of sensors.For example, one or more force sensors underneath or adjacent to thetouch-sensitive surface are, optionally, used to measure force atvarious points on the touch-sensitive surface. In some implementations,force measurements from multiple force sensors are combined (e.g., aweighted average) to determine an estimated force of a contact.Similarly, a pressure-sensitive tip of a stylus is, optionally, used todetermine a pressure of the stylus on the touch-sensitive surface.Alternatively, the size of the contact area detected on thetouch-sensitive surface and/or changes thereto, the capacitance of thetouch-sensitive surface proximate to the contact and/or changes thereto,and/or the resistance of the touch-sensitive surface proximate to thecontact and/or changes thereto are, optionally, used as a substitute forthe force or pressure of the contact on the touch-sensitive surface. Insome implementations, the substitute measurements for contact force orpressure are used directly to determine whether an intensity thresholdhas been exceeded (e.g., the intensity threshold is described in unitscorresponding to the substitute measurements). In some implementations,the substitute measurements for contact force or pressure are convertedto an estimated force or pressure and the estimated force or pressure isused to determine whether an intensity threshold has been exceeded(e.g., the intensity threshold is a pressure threshold measured in unitsof pressure).

As used in the specification and claims, the term “tactile output”refers to physical displacement of a device relative to a previousposition of the device, physical displacement of a component (e.g., atouch-sensitive surface) of a device relative to another component(e.g., housing) of the device, or displacement of the component relativeto a center of mass of the device that will be detected by a user withthe user's sense of touch. For example, in situations where the deviceor the component of the device is in contact with a surface of a userthat is sensitive to touch (e.g., a finger, palm, or other part of auser's hand), the tactile output generated by the physical displacementwill be interpreted by the user as a tactile sensation corresponding toa perceived change in physical characteristics of the device or thecomponent of the device. For example, movement of a touch-sensitivesurface (e.g., a touch-sensitive display or trackpad) is, optionally,interpreted by the user as a “down click” or “up click” of a physicalactuator button. In some cases, a user will feel a tactile sensationsuch as an “down click” or “up click” even when there is no movement ofa physical actuator button associated with the touch-sensitive surfacethat is physically pressed (e.g., displaced) by the user's movements. Asanother example, movement of the touch-sensitive surface is, optionally,interpreted or sensed by the user as “roughness” of the touch-sensitivesurface, even when there is no change in smoothness of thetouch-sensitive surface. While such interpretations of touch by a userwill be subject to the individualized sensory perceptions of the user,there are many sensory perceptions of touch that are common to a largemajority of users. Thus, when a tactile output is described ascorresponding to a particular sensory perception of a user (e.g., an “upclick,” a “down click,” “roughness”), unless otherwise stated, thegenerated tactile output corresponds to physical displacement of thedevice or a component thereof that will generate the described sensoryperception for a typical (or average) user.

It should be appreciated that device 100 is only one example of aportable multifunction device, and that device 100 optionally has moreor fewer components than shown, optionally combines two or morecomponents, or optionally has a different configuration or arrangementof the components. The various components shown in FIG. 1A areimplemented in hardware, software, or a combination of both hardware andsoftware, including one or more signal processing and/or applicationspecific integrated circuits.

Memory 102 optionally includes high-speed random access memory andoptionally also includes non-volatile memory, such as one or moremagnetic disk storage devices, flash memory devices, or othernon-volatile solid-state memory devices. Access to memory 102 by othercomponents of device 100, such as CPU 120 and the peripherals interface118, is, optionally, controlled by memory controller 122.

Peripherals interface 118 can be used to couple input and outputperipherals of the device to CPU 120 and memory 102. The one or moreprocessors 120 run or execute various software programs and/or sets ofinstructions stored in memory 102 to perform various functions fordevice 100 and to process data.

In some embodiments, peripherals interface 118, CPU 120, and memorycontroller 122 are, optionally, implemented on a single chip, such aschip 104. In some other embodiments, they are, optionally, implementedon separate chips.

RF (radio frequency) circuitry 108 receives and sends RF signals, alsocalled electromagnetic signals. RF circuitry 108 converts electricalsignals to/from electromagnetic signals and communicates withcommunications networks and other communications devices via theelectromagnetic signals. RF circuitry 108 optionally includes well-knowncircuitry for performing these functions, including but not limited toan antenna system, an RF transceiver, one or more amplifiers, a tuner,one or more oscillators, a digital signal processor, a CODEC chipset, asubscriber identity module (SIM) card, memory, and so forth. RFcircuitry 108 optionally communicates with networks, such as theInternet, also referred to as the World Wide Web (WWW), an intranetand/or a wireless network, such as a cellular telephone network, awireless local area network (LAN) and/or a metropolitan area network(MAN), and other devices by wireless communication. The wirelesscommunication optionally uses any of a plurality of communicationsstandards, protocols and technologies, including but not limited toGlobal System for Mobile Communications (GSM), Enhanced Data GSMEnvironment (EDGE), high-speed downlink packet access (HSDPA),high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO),HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), nearfield communication (NFC), wideband code division multiple access(W-CDMA), code division multiple access (CDMA), time division multipleaccess (TDMA), Bluetooth, Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a,IEEE 802.11b, IEEE 802.11g and/or IEEE 802.11n), voice over InternetProtocol (VoIP), Wi-MAX, a protocol for e-mail (e.g., Internet messageaccess protocol (IMAP) and/or post office protocol (POP)), instantmessaging (e.g., extensible messaging and presence protocol (XMPP),Session Initiation Protocol for Instant Messaging and PresenceLeveraging Extensions (SIMPLE), Instant Messaging and Presence Service(IMPS)), and/or Short Message Service (SMS), or any other suitablecommunication protocol, including communication protocols not yetdeveloped as of the filing date of this document.

Audio circuitry 110, speaker 111, and microphone 113 provide an audiointerface between a user and device 100. Audio circuitry 110 receivesaudio data from peripherals interface 118, converts the audio data to anelectrical signal, and transmits the electrical signal to speaker 111.Speaker 111 converts the electrical signal to human-audible sound waves.Audio circuitry 110 also receives electrical signals converted bymicrophone 113 from sound waves. Audio circuitry 110 converts theelectrical signal to audio data and transmits the audio data toperipherals interface 118 for processing. Audio data is, optionally,retrieved from and/or transmitted to memory 102 and/or RF circuitry 108by peripherals interface 118. In some embodiments, audio circuitry 110also includes a headset jack (e.g., 212, FIG. 2). The headset jackprovides an interface between audio circuitry 110 and removable audioinput/output peripherals, such as output-only headphones or a headsetwith both output (e.g., a headphone for one or both ears) and input(e.g., a microphone).

I/O subsystem 106 couples input/output peripherals on device 100, suchas touch screen 112 and other input control devices 116, to peripheralsinterface 118. I/O subsystem 106 optionally includes display controller156, optical sensor controller 158, intensity sensor controller 159,haptic feedback controller 161 and one or more input controllers 160 forother input or control devices. The one or more input controllers 160receive/send electrical signals from/to other input or control devices116. The other input control devices 116 optionally include physicalbuttons (e.g., push buttons, rocker buttons, etc.), dials, sliderswitches, joysticks, click wheels, and so forth. In some alternateembodiments, input controller(s) 160 are, optionally, coupled to any (ornone) of the following: a keyboard, infrared port, USB port, and apointer device such as a mouse. The one or more buttons (e.g., 208, FIG.2) optionally include an up/down button for volume control of speaker111 and/or microphone 113. The one or more buttons optionally include apush button (e.g., 206, FIG. 2).

Touch-sensitive display 112 provides an input interface and an outputinterface between the device and a user. Display controller 156 receivesand/or sends electrical signals from/to touch screen 112. Touch screen112 displays visual output to the user. The visual output optionallyincludes graphics, text, icons, video, and any combination thereof(collectively termed “graphics”). In some embodiments, some or all ofthe visual output corresponds to user-interface objects.

Touch screen 112 has a touch-sensitive surface, sensor or set of sensorsthat accepts input from the user based on haptic and/or tactile contact.Touch screen 112 and display controller 156 (along with any associatedmodules and/or sets of instructions in memory 102) detect contact (andany movement or breaking of the contact) on touch screen 112 andconverts the detected contact into interaction with user-interfaceobjects (e.g., one or more soft keys, icons, web pages or images) thatare displayed on touch screen 112. In an exemplary embodiment, a pointof contact between touch screen 112 and the user corresponds to a fingerof the user.

Touch screen 112 optionally uses LCD (liquid crystal display)technology, LPD (light emitting polymer display) technology, or LED(light emitting diode) technology, although other display technologiesare used in other embodiments. Touch screen 112 and display controller156 optionally detect contact and any movement or breaking thereof usingany of a plurality of touch sensing technologies now known or laterdeveloped, including but not limited to capacitive, resistive, infrared,and surface acoustic wave technologies, as well as other proximitysensor arrays or other elements for determining one or more points ofcontact with touch screen 112. In an exemplary embodiment, projectedmutual capacitance sensing technology is used, such as that found in theiPhone®, iPod Touch®, and iPad® from Apple Inc. of Cupertino, Calif.

Touch screen 112 optionally has a video resolution in excess of 100 dpi.In some embodiments, the touch screen has a video resolution ofapproximately 160 dpi. The user optionally makes contact with touchscreen 112 using any suitable object or appendage, such as a stylus, afinger, and so forth. In some embodiments, the user interface isdesigned to work primarily with finger-based contacts and gestures,which can be less precise than stylus-based input due to the larger areaof contact of a finger on the touch screen. In some embodiments, thedevice translates the rough finger-based input into a precisepointer/cursor position or command for performing the actions desired bythe user.

In some embodiments, in addition to the touch screen, device 100optionally includes a touchpad (not shown) for activating ordeactivating particular functions. In some embodiments, the touchpad isa touch-sensitive area of the device that, unlike the touch screen, doesnot display visual output. The touchpad is, optionally, atouch-sensitive surface that is separate from touch screen 112 or anextension of the touch-sensitive surface formed by the touch screen.

Device 100 also includes power system 162 for powering the variouscomponents. Power system 162 optionally includes a power managementsystem, one or more power sources (e.g., battery, alternating current(AC)), a recharging system, a power failure detection circuit, a powerconverter or inverter, a power status indicator (e.g., a light-emittingdiode (LED)) and any other components associated with the generation,management and distribution of power in portable devices.

Device 100 optionally also includes one or more optical sensors 164.FIG. 1A shows an optical sensor coupled to optical sensor controller 158in I/O subsystem 106. Optical sensor 164 optionally includescharge-coupled device (CCD) or complementary metal-oxide semiconductor(CMOS) phototransistors. Optical sensor 164 receives light from theenvironment, projected through one or more lens, and converts the lightto data representing an image. In conjunction with imaging module 143(also called a camera module), optical sensor 164 optionally capturesstill images or video. In some embodiments, an optical sensor is locatedon the back of device 100, opposite touch screen display 112 on thefront of the device, so that the touch screen display is enabled for useas a viewfinder for still and/or video image acquisition. In someembodiments, another optical sensor is located on the front of thedevice so that the user's image is, optionally, obtained forvideoconferencing while the user views the other video conferenceparticipants on the touch screen display.

Device 100 optionally also includes one or more contact intensitysensors 165. FIG. 1A shows a contact intensity sensor coupled tointensity sensor controller 159 in I/O subsystem 106. Contact intensitysensor 165 optionally includes one or more piezoresistive strain gauges,capacitive force sensors, electric force sensors, piezoelectric forcesensors, optical force sensors, capacitive touch-sensitive surfaces, orother intensity sensors (e.g., sensors used to measure the force (orpressure) of a contact on a touch-sensitive surface). Contact intensitysensor 165 receives contact intensity information (e.g., pressureinformation or a proxy for pressure information) from the environment.In some embodiments, at least one contact intensity sensor is collocatedwith, or proximate to, a touch-sensitive surface (e.g., touch-sensitivedisplay system 112). In some embodiments, at least one contact intensitysensor is located on the back of device 100, opposite touch screendisplay 112 which is located on the front of device 100.

Device 100 optionally also includes one or more proximity sensors 166.FIG. 1A shows proximity sensor 166 coupled to peripherals interface 118.Alternately, proximity sensor 166 is coupled to input controller 160 inI/O subsystem 106. In some embodiments, the proximity sensor turns offand disables touch screen 112 when the multifunction device is placednear the user's ear (e.g., when the user is making a phone call).

Device 100 optionally also includes one or more tactile outputgenerators 167. FIG. 1A shows a tactile output generator coupled tohaptic feedback controller 161 in I/O subsystem 106. Tactile outputgenerator 167 optionally includes one or more electroacoustic devicessuch as speakers or other audio components and/or electromechanicaldevices that convert energy into linear motion such as a motor,solenoid, electroactive polymer, piezoelectric actuator, electrostaticactuator, or other tactile output generating component (e.g., acomponent that converts electrical signals into tactile outputs on thedevice). Contact intensity sensor 165 receives tactile feedbackgeneration instructions from haptic feedback module 133 and generatestactile outputs on device 100 that are capable of being sensed by a userof device 100. In some embodiments, at least one tactile outputgenerator is collocated with, or proximate to, a touch-sensitive surface(e.g., touch-sensitive display system 112) and, optionally, generates atactile output by moving the touch-sensitive surface vertically (e.g.,in/out of a surface of device 100) or laterally (e.g., back and forth inthe same plane as a surface of device 100). In some embodiments, atleast one tactile output generator sensor is located on the back ofdevice 100, opposite touch screen display 112 which is located on thefront of device 100.

Device 100 optionally also includes one or more accelerometers 168. FIG.1A shows accelerometer 168 coupled to peripherals interface 118.Alternately, accelerometer 168 is, optionally, coupled to an inputcontroller 160 in I/O subsystem 106. In some embodiments, information isdisplayed on the touch screen display in a portrait view or a landscapeview based on an analysis of data received from the one or moreaccelerometers. Device 100 optionally includes, in addition toaccelerometer(s) 168, a magnetometer (not shown) and a GPS (or GLONASSor other global navigation system) receiver (not shown) for obtaininginformation concerning the location and orientation (e.g., portrait orlandscape) of device 100.

In some embodiments, the software components stored in memory 102include operating system 126, communication module (or set ofinstructions) 128, contact/motion module (or set of instructions) 130,graphics module (or set of instructions) 132, text input module (or setof instructions) 134, Global Positioning System (GPS) module (or set ofinstructions) 135, and applications (or sets of instructions) 136.Furthermore, in some embodiments memory 102 stores device/globalinternal state 157, as shown in FIGS. 1A and 3. Device/global internalstate 157 includes one or more of: active application state, indicatingwhich applications, if any, are currently active; display state,indicating what applications, views or other information occupy variousregions of touch screen display 112; sensor state, including informationobtained from the device's various sensors and input control devices116; and location information concerning the device's location and/orattitude.

Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, WINDOWS, oran embedded operating system such as VxWorks) includes various softwarecomponents and/or drivers for controlling and managing general systemtasks (e.g., memory management, storage device control, powermanagement, etc.) and facilitates communication between various hardwareand software components.

Communication module 128 facilitates communication with other devicesover one or more external ports 124 and also includes various softwarecomponents for handling data received by RF circuitry 108 and/orexternal port 124. External port 124 (e.g., Universal Serial Bus (USB),FIREWIRE, etc.) is adapted for coupling directly to other devices orindirectly over a network (e.g., the Internet, wireless LAN, etc.). Insome embodiments, the external port is a multi-pin (e.g., 30-pin)connector that is the same as, or similar to and/or compatible with the30-pin connector used on iPod (trademark of Apple Inc.) devices.

Contact/motion module 130 optionally detects contact with touch screen112 (in conjunction with display controller 156) and other touchsensitive devices (e.g., a touchpad or physical click wheel).Contact/motion module 130 includes various software components forperforming various operations related to detection of contact, such asdetermining if contact has occurred (e.g., detecting a finger-downevent), determining an intensity of the contact (e.g., the force orpressure of the contact or a substitute for the force or pressure of thecontact) determining if there is movement of the contact and trackingthe movement across the touch-sensitive surface (e.g., detecting one ormore finger-dragging events), and determining if the contact has ceased(e.g., detecting a finger-up event or a break in contact).Contact/motion module 130 receives contact data from the touch-sensitivesurface. Determining movement of the point of contact, which isrepresented by a series of contact data, optionally includes determiningspeed (magnitude), velocity (magnitude and direction), and/or anacceleration (a change in magnitude and/or direction) of the point ofcontact. These operations are, optionally, applied to single contacts(e.g., one finger contacts) or to multiple simultaneous contacts (e.g.,“multitouch”/multiple finger contacts). In some embodiments,contact/motion module 130 and display controller 156 detect contact on atouchpad.

In some embodiments, contact/motion module 130 uses a set of one or moreintensity thresholds to determine whether an operation has beenperformed by a user (e.g., to determine whether a user has “clicked” onan icon). In some embodiments at least a subset of the intensitythresholds are determined in accordance with software parameters (e.g.,the intensity thresholds are not determined by the activation thresholdsof particular physical actuators and can be adjusted without changingthe physical hardware of device 100). For example, a mouse “click”threshold of a trackpad or touch screen display can be set to any of alarge range of predefined thresholds values without changing thetrackpad or touch screen display hardware. Additionally, in someimplementations a user of the device is provided with software settingsfor adjusting one or more of the set of intensity thresholds (e.g., byadjusting individual intensity thresholds and/or by adjusting aplurality of intensity thresholds at once with a system-level click“intensity” parameter).

Contact/motion module 130 optionally detects a gesture input by a user.Different gestures on the touch-sensitive surface have different contactpatterns and intensities. Thus, a gesture is, optionally, detected bydetecting a particular contact pattern. For example, detecting a fingertap gesture includes detecting a finger-down event followed by detectinga finger-up (lift off) event at the same position (or substantially thesame position) as the finger-down event (e.g., at the position of anicon). As another example, detecting a finger swipe gesture on thetouch-sensitive surface includes detecting a finger-down event followedby detecting one or more finger-dragging events, and subsequentlyfollowed by detecting a finger-up (lift off) event.

Graphics module 132 includes various known software components forrendering and displaying graphics on touch screen 112 or other display,including components for changing the visual impact (e.g., brightness,transparency, saturation, contrast or other visual property) of graphicsthat are displayed. As used herein, the term “graphics” includes anyobject that can be displayed to a user, including without limitationtext, web pages, icons (such as user-interface objects including softkeys), digital images, videos, animations and the like.

In some embodiments, graphics module 132 stores data representinggraphics to be used. Each graphic is, optionally, assigned acorresponding code. Graphics module 132 receives, from applicationsetc., one or more codes specifying graphics to be displayed along with,if necessary, coordinate data and other graphic property data, and thengenerates screen image data to output to display controller 156.

Haptic feedback module 133 includes various software components forgenerating instructions used by tactile output generator(s) 167 toproduce tactile outputs at one or more locations on device 100 inresponse to user interactions with device 100.

Text input module 134, which is, optionally, a component of graphicsmodule 132, provides soft keyboards for entering text in variousapplications (e.g., contacts 137, e-mail 140, IM 141, browser 147, andany other application that needs text input).

GPS module 135 determines the location of the device and provides thisinformation for use in various applications (e.g., to telephone 138 foruse in location-based dialing, to camera 143 as picture/video metadata,and to applications that provide location-based services such as weatherwidgets, local yellow page widgets, and map/navigation widgets).

Applications 136 optionally include the following modules (or sets ofinstructions), or a subset or superset thereof:

-   -   contacts module 137 (sometimes called an address book or contact        list);    -   telephone module 138;    -   video conferencing module 139;    -   e-mail client module 140;    -   instant messaging (IM) module 141;    -   workout support module 142;    -   camera module 143 for still and/or video images;    -   image management module 144;    -   browser module 147;    -   calendar module 148;    -   widget modules 149, which optionally include one or more of:        weather widget 149-1, stocks widget 149-2, calculator widget        149-3, alarm clock widget 149-4, dictionary widget 149-5, and        other widgets obtained by the user, as well as user-created        widgets 149-6;    -   widget creator module 150 for making user-created widgets 149-6;    -   search module 151;    -   video and music player module 152, which is, optionally, made up        of a video player module and a music player module;    -   notes module 153;    -   map module 154; and/or    -   online video module 155.

Examples of other applications 136 that are, optionally, stored inmemory 102 include other word processing applications, other imageediting applications, drawing applications, presentation applications,JAVA-enabled applications, encryption, digital rights management, voicerecognition, and voice replication.

In conjunction with touch screen 112, display controller 156, contactmodule 130, graphics module 132, and text input module 134, contactsmodule 137 are, optionally, used to manage an address book or contactlist (e.g., stored in application internal state 192 of contacts module137 in memory 102 or memory 370), including: adding name(s) to theaddress book; deleting name(s) from the address book; associatingtelephone number(s), e-mail address(es), physical address(es) or otherinformation with a name; associating an image with a name; categorizingand sorting names; providing telephone numbers or e-mail addresses toinitiate and/or facilitate communications by telephone 138, videoconference 139, e-mail 140, or IM 141; and so forth.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, contact module130, graphics module 132, and text input module 134, telephone module138 are, optionally, used to enter a sequence of characterscorresponding to a telephone number, access one or more telephonenumbers in address book 137, modify a telephone number that has beenentered, dial a respective telephone number, conduct a conversation anddisconnect or hang up when the conversation is completed. As notedabove, the wireless communication optionally uses any of a plurality ofcommunications standards, protocols and technologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, optical sensor164, optical sensor controller 158, contact module 130, graphics module132, text input module 134, contact list 137, and telephone module 138,videoconferencing module 139 includes executable instructions toinitiate, conduct, and terminate a video conference between a user andone or more other participants in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact module 130, graphics module 132, and text inputmodule 134, e-mail client module 140 includes executable instructions tocreate, send, receive, and manage e-mail in response to userinstructions. In conjunction with image management module 144, e-mailclient module 140 makes it very easy to create and send e-mails withstill or video images taken with camera module 143.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact module 130, graphics module 132, and text inputmodule 134, the instant messaging module 141 includes executableinstructions to enter a sequence of characters corresponding to aninstant message, to modify previously entered characters, to transmit arespective instant message (for example, using a Short Message Service(SMS) or Multimedia Message Service (MMS) protocol for telephony-basedinstant messages or using XMPP, SIMPLE, or IMPS for Internet-basedinstant messages), to receive instant messages and to view receivedinstant messages. In some embodiments, transmitted and/or receivedinstant messages optionally include graphics, photos, audio files, videofiles and/or other attachments as are supported in a MMS and/or anEnhanced Messaging Service (EMS). As used herein, “instant messaging”refers to both telephony-based messages (e.g., messages sent using SMSor MMS) and Internet-based messages (e.g., messages sent using XMPP,SIMPLE, or IMPS).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact module 130, graphics module 132, text inputmodule 134, GPS module 135, map module 154, and music player module 146,workout support module 142 includes executable instructions to createworkouts (e.g., with time, distance, and/or calorie burning goals);communicate with workout sensors (sports devices); receive workoutsensor data; calibrate sensors used to monitor a workout; select andplay music for a workout; and display, store and transmit workout data.

In conjunction with touch screen 112, display controller 156, opticalsensor(s) 164, optical sensor controller 158, contact module 130,graphics module 132, and image management module 144, camera module 143includes executable instructions to capture still images or video(including a video stream) and store them into memory 102, modifycharacteristics of a still image or video, or delete a still image orvideo from memory 102.

In conjunction with touch screen 112, display controller 156, contactmodule 130, graphics module 132, text input module 134, and cameramodule 143, image management module 144 includes executable instructionsto arrange, modify (e.g., edit), or otherwise manipulate, label, delete,present (e.g., in a digital slide show or album), and store still and/orvideo images.

In conjunction with RF circuitry 108, touch screen 112, display systemcontroller 156, contact module 130, graphics module 132, and text inputmodule 134, browser module 147 includes executable instructions tobrowse the Internet in accordance with user instructions, includingsearching, linking to, receiving, and displaying web pages or portionsthereof, as well as attachments and other files linked to web pages.

In conjunction with RF circuitry 108, touch screen 112, display systemcontroller 156, contact module 130, graphics module 132, text inputmodule 134, e-mail client module 140, and browser module 147, calendarmodule 148 includes executable instructions to create, display, modify,and store calendars and data associated with calendars (e.g., calendarentries, to do lists, etc.) in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, display systemcontroller 156, contact module 130, graphics module 132, text inputmodule 134, and browser module 147, widget modules 149 aremini-applications that are, optionally, downloaded and used by a user(e.g., weather widget 149-1, stocks widget 149-2, calculator widget149-3, alarm clock widget 149-4, and dictionary widget 149-5) or createdby the user (e.g., user-created widget 149-6). In some embodiments, awidget includes an HTML (Hypertext Markup Language) file, a CSS(Cascading Style Sheets) file, and a JavaScript file. In someembodiments, a widget includes an XML (Extensible Markup Language) fileand a JavaScript file (e.g., Yahoo! Widgets).

In conjunction with RF circuitry 108, touch screen 112, display systemcontroller 156, contact module 130, graphics module 132, text inputmodule 134, and browser module 147, the widget creator module 150 are,optionally, used by a user to create widgets (e.g., turning auser-specified portion of a web page into a widget).

In conjunction with touch screen 112, display system controller 156,contact module 130, graphics module 132, and text input module 134,search module 151 includes executable instructions to search for text,music, sound, image, video, and/or other files in memory 102 that matchone or more search criteria (e.g., one or more user-specified searchterms) in accordance with user instructions.

In conjunction with touch screen 112, display system controller 156,contact module 130, graphics module 132, audio circuitry 110, speaker111, RF circuitry 108, and browser module 147, video and music playermodule 152 includes executable instructions that allow the user todownload and play back recorded music and other sound files stored inone or more file formats, such as MP3 or AAC files, and executableinstructions to display, present or otherwise play back videos (e.g., ontouch screen 112 or on an external, connected display via external port124). In some embodiments, device 100 optionally includes thefunctionality of an MP3 player, such as an iPod (trademark of AppleInc.).

In conjunction with touch screen 112, display controller 156, contactmodule 130, graphics module 132, and text input module 134, notes module153 includes executable instructions to create and manage notes, to dolists, and the like in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, display systemcontroller 156, contact module 130, graphics module 132, text inputmodule 134, GPS module 135, and browser module 147, map module 154 are,optionally, used to receive, display, modify, and store maps and dataassociated with maps (e.g., driving directions; data on stores and otherpoints of interest at or near a particular location; and otherlocation-based data) in accordance with user instructions.

In conjunction with touch screen 112, display system controller 156,contact module 130, graphics module 132, audio circuitry 110, speaker111, RF circuitry 108, text input module 134, e-mail client module 140,and browser module 147, online video module 155 includes instructionsthat allow the user to access, browse, receive (e.g., by streamingand/or download), play back (e.g., on the touch screen or on anexternal, connected display via external port 124), send an e-mail witha link to a particular online video, and otherwise manage online videosin one or more file formats, such as H.264. In some embodiments, instantmessaging module 141, rather than e-mail client module 140, is used tosend a link to a particular online video.

Each of the above identified modules and applications correspond to aset of executable instructions for performing one or more functionsdescribed above and the methods described in this application (e.g., thecomputer-implemented methods and other information processing methodsdescribed herein). These modules (i.e., sets of instructions) need notbe implemented as separate software programs, procedures or modules, andthus various subsets of these modules are, optionally, combined orotherwise re-arranged in various embodiments. In some embodiments,memory 102 optionally stores a subset of the modules and data structuresidentified above. Furthermore, memory 102 optionally stores additionalmodules and data structures not described above.

In some embodiments, device 100 is a device where operation of apredefined set of functions on the device is performed exclusivelythrough a touch screen and/or a touchpad. By using a touch screen and/ora touchpad as the primary input control device for operation of device100, the number of physical input control devices (such as push buttons,dials, and the like) on device 100 is, optionally, reduced.

The predefined set of functions that are performed exclusively through atouch screen and/or a touchpad optionally include navigation betweenuser interfaces. In some embodiments, the touchpad, when touched by theuser, navigates device 100 to a main, home, or root menu from any userinterface that is displayed on device 100. In such embodiments, a “menubutton” is implemented using a touchpad. In some other embodiments, themenu button is a physical push button or other physical input controldevice instead of a touchpad.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments. In some embodiments,memory 102 (in FIG. 1A) or 370 (FIG. 3) includes event sorter 170 (e.g.,in operating system 126) and a respective application 136-1 (e.g., anyof the aforementioned applications 137-151, 155, 380-390).

Event sorter 170 receives event information and determines theapplication 136-1 and application view 191 of application 136-1 to whichto deliver the event information. Event sorter 170 includes eventmonitor 171 and event dispatcher module 174. In some embodiments,application 136-1 includes application internal state 192, whichindicates the current application view(s) displayed on touch sensitivedisplay 112 when the application is active or executing. In someembodiments, device/global internal state 157 is used by event sorter170 to determine which application(s) is (are) currently active, andapplication internal state 192 is used by event sorter 170 to determineapplication views 191 to which to deliver event information.

In some embodiments, application internal state 192 includes additionalinformation, such as one or more of: resume information to be used whenapplication 136-1 resumes execution, user interface state informationthat indicates information being displayed or that is ready for displayby application 136-1, a state queue for enabling the user to go back toa prior state or view of application 136-1, and a redo/undo queue ofprevious actions taken by the user.

Event monitor 171 receives event information from peripherals interface118. Event information includes information about a sub-event (e.g., auser touch on touch-sensitive display 112, as part of a multi-touchgesture). Peripherals interface 118 transmits information it receivesfrom I/O subsystem 106 or a sensor, such as proximity sensor 166,accelerometer(s) 168, and/or microphone 113 (through audio circuitry110). Information that peripherals interface 118 receives from I/Osubsystem 106 includes information from touch-sensitive display 112 or atouch-sensitive surface.

In some embodiments, event monitor 171 sends requests to the peripheralsinterface 118 at predetermined intervals. In response, peripheralsinterface 118 transmits event information. In other embodiments,peripheral interface 118 transmits event information only when there isa significant event (e.g., receiving an input above a predeterminednoise threshold and/or for more than a predetermined duration).

In some embodiments, event sorter 170 also includes a hit viewdetermination module 172 and/or an active event recognizer determinationmodule 173.

Hit view determination module 172 provides software procedures fordetermining where a sub-event has taken place within one or more views,when touch sensitive display 112 displays more than one view. Views aremade up of controls and other elements that a user can see on thedisplay.

Another aspect of the user interface associated with an application is aset of views, sometimes herein called application views or userinterface windows, in which information is displayed and touch-basedgestures occur. The application views (of a respective application) inwhich a touch is detected optionally correspond to programmatic levelswithin a programmatic or view hierarchy of the application. For example,the lowest level view in which a touch is detected is, optionally,called the hit view, and the set of events that are recognized as properinputs are, optionally, determined based, at least in part, on the hitview of the initial touch that begins a touch-based gesture.

Hit view determination module 172 receives information related tosub-events of a touch-based gesture. When an application has multipleviews organized in a hierarchy, hit view determination module 172identifies a hit view as the lowest view in the hierarchy which shouldhandle the sub-event. In most circumstances, the hit view is the lowestlevel view in which an initiating sub-event occurs (i.e., the firstsub-event in the sequence of sub-events that form an event or potentialevent). Once the hit view is identified by the hit view determinationmodule, the hit view typically receives all sub-events related to thesame touch or input source for which it was identified as the hit view.

Active event recognizer determination module 173 determines which viewor views within a view hierarchy should receive a particular sequence ofsub-events. In some embodiments, active event recognizer determinationmodule 173 determines that only the hit view should receive a particularsequence of sub-events. In other embodiments, active event recognizerdetermination module 173 determines that all views that include thephysical location of a sub-event are actively involved views, andtherefore determines that all actively involved views should receive aparticular sequence of sub-events. In other embodiments, even if touchsub-events were entirely confined to the area associated with oneparticular view, views higher in the hierarchy would still remain asactively involved views.

Event dispatcher module 174 dispatches the event information to an eventrecognizer (e.g., event recognizer 180). In embodiments including activeevent recognizer determination module 173, event dispatcher module 174delivers the event information to an event recognizer determined byactive event recognizer determination module 173. In some embodiments,event dispatcher module 174 stores in an event queue the eventinformation, which is retrieved by a respective event receiver module182.

In some embodiments, operating system 126 includes event sorter 170.Alternatively, application 136-1 includes event sorter 170. In yet otherembodiments, event sorter 170 is a stand-alone module, or a part ofanother module stored in memory 102, such as contact/motion module 130.

In some embodiments, application 136-1 includes a plurality of eventhandlers 190 and one or more application views 191, each of whichincludes instructions for handling touch events that occur within arespective view of the application's user interface. Each applicationview 191 of the application 136-1 includes one or more event recognizers180. Typically, a respective application view 191 includes a pluralityof event recognizers 180. In other embodiments, one or more of eventrecognizers 180 are part of a separate module, such as a user interfacekit (not shown) or a higher level object from which application 136-1inherits methods and other properties. In some embodiments, a respectiveevent handler 190 includes one or more of: data updater 176, objectupdater 177, GUI updater 178, and/or event data 179 received from eventsorter 170. Event handler 190 optionally utilizes or calls data updater176, object updater 177 or GUI updater 178 to update the applicationinternal state 192. Alternatively, one or more of the application views191 includes one or more respective event handlers 190. Also, in someembodiments, one or more of data updater 176, object updater 177, andGUI updater 178 are included in a respective application view 191.

A respective event recognizer 180 receives event information (e.g.,event data 179) from event sorter 170, and identifies an event from theevent information. Event recognizer 180 includes event receiver 182 andevent comparator 184. In some embodiments, event recognizer 180 alsoincludes at least a subset of: metadata 183, and event deliveryinstructions 188 (which optionally include sub-event deliveryinstructions).

Event receiver 182 receives event information from event sorter 170. Theevent information includes information about a sub-event, for example, atouch or a touch movement. Depending on the sub-event, the eventinformation also includes additional information, such as location ofthe sub-event. When the sub-event concerns motion of a touch, the eventinformation optionally also includes speed and direction of thesub-event. In some embodiments, events include rotation of the devicefrom one orientation to another (e.g., from a portrait orientation to alandscape orientation, or vice versa), and the event informationincludes corresponding information about the current orientation (alsocalled device attitude) of the device.

Event comparator 184 compares the event information to predefined eventor sub-event definitions and, based on the comparison, determines anevent or sub-event, or determines or updates the state of an event orsub-event. In some embodiments, event comparator 184 includes eventdefinitions 186. Event definitions 186 contain definitions of events(e.g., predefined sequences of sub-events), for example, event 1(187-1), event 2 (187-2), and others. In some embodiments, sub-events inan event 187 include, for example, touch begin, touch end, touchmovement, touch cancellation, and multiple touching. In one example, thedefinition for event 1 (187-1) is a double tap on a displayed object.The double tap, for example, comprises a first touch (touch begin) onthe displayed object for a predetermined phase, a first lift-off (touchend) for a predetermined phase, a second touch (touch begin) on thedisplayed object for a predetermined phase, and a second lift-off (touchend) for a predetermined phase. In another example, the definition forevent 2 (187-2) is a dragging on a displayed object. The dragging, forexample, comprises a touch (or contact) on the displayed object for apredetermined phase, a movement of the touch across touch-sensitivedisplay 112, and lift-off of the touch (touch end). In some embodiments,the event also includes information for one or more associated eventhandlers 190.

In some embodiments, event definition 187 includes a definition of anevent for a respective user-interface object. In some embodiments, eventcomparator 184 performs a hit test to determine which user-interfaceobject is associated with a sub-event. For example, in an applicationview in which three user-interface objects are displayed ontouch-sensitive display 112, when a touch is detected on touch-sensitivedisplay 112, event comparator 184 performs a hit test to determine whichof the three user-interface objects is associated with the touch(sub-event). If each displayed object is associated with a respectiveevent handler 190, the event comparator uses the result of the hit testto determine which event handler 190 should be activated. For example,event comparator 184 selects an event handler associated with thesub-event and the object triggering the hit test.

In some embodiments, the definition for a respective event 187 alsoincludes delayed actions that delay delivery of the event informationuntil after it has been determined whether the sequence of sub-eventsdoes or does not correspond to the event recognizer's event type.

When a respective event recognizer 180 determines that the series ofsub-events do not match any of the events in event definitions 186, therespective event recognizer 180 enters an event impossible, eventfailed, or event ended state, after which it disregards subsequentsub-events of the touch-based gesture. In this situation, other eventrecognizers, if any, that remain active for the hit view continue totrack and process sub-events of an ongoing touch-based gesture.

In some embodiments, a respective event recognizer 180 includes metadata183 with configurable properties, flags, and/or lists that indicate howthe event delivery system should perform sub-event delivery to activelyinvolved event recognizers. In some embodiments, metadata 183 includesconfigurable properties, flags, and/or lists that indicate how eventrecognizers interact, or are enabled to interact, with one another. Insome embodiments, metadata 183 includes configurable properties, flags,and/or lists that indicate whether sub-events are delivered to varyinglevels in the view or programmatic hierarchy.

In some embodiments, a respective event recognizer 180 activates eventhandler 190 associated with an event when one or more particularsub-events of an event are recognized. In some embodiments, a respectiveevent recognizer 180 delivers event information associated with theevent to event handler 190. Activating an event handler 190 is distinctfrom sending (and deferred sending) sub-events to a respective hit view.In some embodiments, event recognizer 180 throws a flag associated withthe recognized event, and event handler 190 associated with the flagcatches the flag and performs a predefined process.

In some embodiments, event delivery instructions 188 include sub-eventdelivery instructions that deliver event information about a sub-eventwithout activating an event handler. Instead, the sub-event deliveryinstructions deliver event information to event handlers associated withthe series of sub-events or to actively involved views. Event handlersassociated with the series of sub-events or with actively involved viewsreceive the event information and perform a predetermined process.

In some embodiments, data updater 176 creates and updates data used inapplication 136-1. For example, data updater 176 updates the telephonenumber used in contacts module 137, or stores a video file used in videoplayer module 145. In some embodiments, object updater 177 creates andupdates objects used in application 136-1. For example, object updater177 creates a new user-interface object or updates the position of auser-interface object. GUI updater 178 updates the GUI. For example, GUIupdater 178 prepares display information and sends it to graphics module132 for display on a touch-sensitive display.

In some embodiments, event handler(s) 190 includes or has access to dataupdater 176, object updater 177, and GUI updater 178. In someembodiments, data updater 176, object updater 177, and GUI updater 178are included in a single module of a respective application 136-1 orapplication view 191. In other embodiments, they are included in two ormore software modules.

It shall be understood that the foregoing discussion regarding eventhandling of user touches on touch-sensitive displays also applies toother forms of user inputs to operate multifunction devices 100 withinput-devices, not all of which are initiated on touch screens. Forexample, mouse movement and mouse button presses, optionally coordinatedwith single or multiple keyboard presses or holds; contact movementssuch as taps, drags, scrolls, etc., on touch-pads; pen stylus inputs;movement of the device; oral instructions; detected eye movements;biometric inputs; and/or any combination thereof are optionally utilizedas inputs corresponding to sub-events which define an event to berecognized.

FIG. 2 illustrates a portable multifunction device 100 having a touchscreen 112 in accordance with some embodiments. The touch screenoptionally displays one or more graphics within user interface (UI) 200.In this embodiment, as well as others described below, a user is enabledto select one or more of the graphics by making a gesture on thegraphics, for example, with one or more fingers 202 (not drawn to scalein the figure) or one or more styluses 203 (not drawn to scale in thefigure). In some embodiments, selection of one or more graphics occurswhen the user breaks contact with the one or more graphics. In someembodiments, the gesture optionally includes one or more taps, one ormore swipes (from left to right, right to left, upward and/or downward)and/or a rolling of a finger (from right to left, left to right, upwardand/or downward) that has made contact with device 100. In someimplementations or circumstances, inadvertent contact with a graphicdoes not select the graphic. For example, a swipe gesture that sweepsover an application icon optionally does not select the correspondingapplication when the gesture corresponding to selection is a tap.

Device 100 optionally also includes one or more physical buttons, suchas “home” or menu button 204. As described previously, menu button 204is, optionally, used to navigate to any application 136 in a set ofapplications that are, optionally executed on device 100. Alternatively,in some embodiments, the menu button is implemented as a soft key in aGUI displayed on touch screen 112.

In one embodiment, device 100 includes touch screen 112, menu button204, push button 206 for powering the device on/off and locking thedevice, volume adjustment button(s) 208, Subscriber Identity Module(SIM) card slot 210, head set jack 212, and docking/charging externalport 124. Push button 206 is, optionally, used to turn the power on/offon the device by depressing the button and holding the button in thedepressed state for a predefined time interval; to lock the device bydepressing the button and releasing the button before the predefinedtime interval has elapsed; and/or to unlock the device or initiate anunlock process. In an alternative embodiment, device 100 also acceptsverbal input for activation or deactivation of some functions throughmicrophone 113. Device 100 also, optionally, includes one or morecontact intensity sensors 165 for detecting intensity of contacts ontouch screen 112 and/or one or more tactile output generators 167 forgenerating tactile outputs for a user of device 100.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments. Device 300 need not be portable. In some embodiments,device 300 is a laptop computer, a desktop computer, a tablet computer,a multimedia player device, a navigation device, an educational device(such as a child's learning toy), a gaming system, or a control device(e.g., a home or industrial controller). Device 300 typically includesone or more processing units (CPU's) 310, one or more network or othercommunications interfaces 360, memory 370, and one or more communicationbuses 320 for interconnecting these components. Communication buses 320optionally include circuitry (sometimes called a chipset) thatinterconnects and controls communications between system components.Device 300 includes input/output (I/O) interface 330 comprising display340, which is typically a touch screen display. I/O interface 330 alsooptionally includes a keyboard and/or mouse (or other pointing device)350 and touchpad 355, tactile output generator 357 for generatingtactile outputs on device 300 (e.g., similar to tactile outputgenerator(s) 167 described above with reference to FIG. 1A), sensors 359(e.g., optical, acceleration, proximity, touch-sensitive, and/or contactintensity sensors similar to contact intensity sensor(s) 165 describedabove with reference to FIG. 1A). Memory 370 includes high-speed randomaccess memory, such as DRAM, SRAM, DDR RAM or other random access solidstate memory devices; and optionally includes non-volatile memory, suchas one or more magnetic disk storage devices, optical disk storagedevices, flash memory devices, or other non-volatile solid state storagedevices. Memory 370 optionally includes one or more storage devicesremotely located from CPU(s) 310. In some embodiments, memory 370 storesprograms, modules, and data structures analogous to the programs,modules, and data structures stored in memory 102 of portablemultifunction device 100 (FIG. 1A), or a subset thereof. Furthermore,memory 370 optionally stores additional programs, modules, and datastructures not present in memory 102 of portable multifunction device100. For example, memory 370 of device 300 optionally stores drawingmodule 380, presentation module 382, word processing module 384, websitecreation module 386, disk authoring module 388, and/or spreadsheetmodule 390, while memory 102 of portable multifunction device 100 (FIG.1A) optionally does not store these modules.

Each of the above identified elements in FIG. 3 are, optionally, storedin one or more of the previously mentioned memory devices. Each of theabove identified modules corresponds to a set of instructions forperforming a function described above. The above identified modules orprograms (i.e., sets of instructions) need not be implemented asseparate software programs, procedures or modules, and thus varioussubsets of these modules are, optionally, combined or otherwisere-arranged in various embodiments. In some embodiments, memory 370optionally stores a subset of the modules and data structures identifiedabove. Furthermore, memory 370 optionally stores additional modules anddata structures not described above.

Attention is now directed towards embodiments of user interfaces (“UI”)that is, optionally, implemented on portable multifunction device 100.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on portable multifunction device 100 in accordance withsome embodiments. Similar user interfaces are, optionally, implementedon device 300. In some embodiments, user interface 400 includes thefollowing elements, or a subset or superset thereof:

-   -   Signal strength indicator(s) 402 for wireless communication(s),        such as cellular and Wi-Fi signals;    -   Time 404;    -   Bluetooth indicator 405;    -   Battery status indicator 406;    -   Tray 408 with icons for frequently used applications, such as:        -   Icon 416 for telephone module 138, labeled “Phone,” which            optionally includes an indicator 414 of the number of missed            calls or voicemail messages;        -   Icon 418 for e-mail client module 140, labeled “Mail,” which            optionally includes an indicator 410 of the number of unread            e-mails;        -   Icon 420 for browser module 147, labeled “Browser;” and Icon            422 for video and music player module 152, also referred to            as iPod (trademark of Apple Inc.) module 152, labeled            “iPod;” and    -   Icons for other applications, such as:        -   Icon 424 for IM module 141, labeled “Text;”        -   Icon 426 for calendar module 148, labeled “Calendar;”        -   Icon 428 for image management module 144, labeled “Photos;”        -   Icon 430 for camera module 143, labeled “Camera;”        -   Icon 432 for online video module 155, labeled “Online Video”        -   Icon 434 for stocks widget 149-2, labeled “Stocks;”        -   Icon 436 for map module 154, labeled “Map;”        -   Icon 438 for weather widget 149-1, labeled “Weather;”        -   Icon 440 for alarm clock widget 149-4, labeled “Clock;”        -   Icon 442 for workout support module 142, labeled “Workout            Support;”        -   Icon 444 for notes module 153, labeled “Notes;” and        -   Icon 446 for a settings application or module, which            provides access to settings for device 100 and its various            applications 136.

It should be noted that the icon labels illustrated in FIG. 4A aremerely exemplary. For example, icon 422 for video and music playermodule 152 are labeled “Music” or “Music Player.” Other labels are,optionally, used for various application icons. In some embodiments, alabel for a respective application icon includes a name of anapplication corresponding to the respective application icon. In someembodiments, a label for a particular application icon is distinct froma name of an application corresponding to the particular applicationicon.

FIG. 4B illustrates an exemplary user interface on a device (e.g.,device 300, FIG. 3) with a touch-sensitive surface 451 (e.g., a tabletor touchpad 355, FIG. 3) that is separate from the display 450 (e.g.,touch screen display 112). Device 300 also, optionally, includes one ormore contact intensity sensors (e.g., one or more of sensors 357) fordetecting intensity of contacts on touch-sensitive surface 451 and/orone or more tactile output generators 359 for generating tactile outputsfor a user of device 300.

Although some of the examples which follow will be given with referenceto inputs on touch screen display 112 (where the touch sensitive surfaceand the display are combined), in some embodiments, the device detectsinputs on a touch-sensitive surface that is separate from the display,as shown in FIG. 4B. In some embodiments the touch sensitive surface(e.g., 451 in FIG. 4B) has a primary axis (e.g., 452 in FIG. 4B) thatcorresponds to a primary axis (e.g., 453 in FIG. 4B) on the display(e.g., 450). In accordance with these embodiments, the device detectscontacts (e.g., 460 and 462 in FIG. 4B) with the touch-sensitive surface451 at locations that correspond to respective locations on the display(e.g., in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470).In this way, user inputs (e.g., contacts 460 and 462, and movementsthereof) detected by the device on the touch-sensitive surface (e.g.,451 in FIG. 4B) are used by the device to manipulate the user interfaceon the display (e.g., 450 in FIG. 4B) of the multifunction device whenthe touch-sensitive surface is separate from the display. It should beunderstood that similar methods are, optionally, used for other userinterfaces described herein.

Additionally, while the following examples are given primarily withreference to finger inputs (e.g., finger contacts, finger tap gestures,finger swipe gestures), it should be understood that, in someembodiments, one or more of the finger inputs are replaced with inputfrom another input device (e.g., a mouse based input or stylus input).For example, a swipe gesture is, optionally, replaced with a mouse click(e.g., instead of a contact) followed by movement of the cursor alongthe path of the swipe (e.g., instead of movement of the contact). Asanother example, a tap gesture is, optionally, replaced with a mouseclick while the cursor is located over the location of the tap gesture(e.g., instead of detection of the contact followed by ceasing to detectthe contact). Similarly, when multiple user inputs are simultaneouslydetected, it should be understood that multiple computer mice are,optionally, used simultaneously, or a mouse and finger contacts are,optionally, used simultaneously.

As used herein, the term “focus selector” refers to an input elementthat indicates a current part of a user interface with which a user isinteracting. In some implementations that include a cursor or otherlocation marker, the cursor acts as a “focus selector,” so that when aninput (e.g., a press input) is detected on a touch-sensitive surface(e.g., touchpad 355 in FIG. 3 or touch-sensitive surface 451 in FIG. 4B)while the cursor is over a particular user interface element (e.g., abutton, window, slider or other user interface element), the particularuser interface element is adjusted in accordance with the detectedinput. In some implementations that include a touch-screen display(e.g., touch-sensitive display system 112 in FIG. 1A or touch screen 112in FIG. 4A) that enables direct interaction with user interface elementson the touch-screen display, a detected contact on the touch-screen actsas a “focus selector,” so that when an input (e.g., a press input by thecontact) is detected on the touch-screen display at a location of aparticular user interface element (e.g., a button, window, slider orother user interface element), the particular user interface element isadjusted in accordance with the detected input. In some implementationsfocus is moved from one region of a user interface to another region ofthe user interface without corresponding movement of a cursor ormovement of a contact on a touch-screen display (e.g., by using a tabkey or arrow keys to move focus from one button to another button); inthese implementations, the focus selector moves in accordance withmovement of focus between different regions of the user interface.Without regard to the specific form taken by the focus selector, thefocus selector is generally the user interface element (or contact on atouch-screen display) that is controlled by the user so as tocommunicate the user's intended interaction with the user interface(e.g., by indicating, to the device, the element of the user interfacewith which the user is intending to interact). For example, the locationof a focus selector (e.g., a cursor, a contact or a selection box) overa respective button while a press input is detected on thetouch-sensitive surface (e.g., a touchpad or touch screen) will indicatethat the user is intending to activate the respective button (as opposedto other user interface elements shown on a display of the device).

The user interface figures described below include various intensitydiagrams that show the current intensity of the contact on thetouch-sensitive surface relative to one or more intensity thresholds(e.g., a contact detection intensity threshold IT₀, a light pressintensity threshold IT_(L), a deep press intensity threshold IT_(D),and/or one or more other intensity thresholds). This intensity diagramis typically not part of the displayed user interface, but is providedto aid in the interpretation of the figures. In some embodiments, thelight press intensity threshold corresponds to an intensity at which thedevice will perform operations typically associated with clicking abutton of a physical mouse or a trackpad. In some embodiments, the deeppress intensity threshold corresponds to an intensity at which thedevice will perform operations that are different from operationstypically associated with clicking a button of a physical mouse or atrackpad. In some embodiments, when a contact is detected with anintensity below the light press intensity threshold (e.g., and above anominal contact-detection intensity threshold IT₀ below which thecontact is no longer detected), the device will move a focus selector inaccordance with movement of the contact on the touch-sensitive surfacewithout performing an operation associated with the light pressintensity threshold or the deep press intensity threshold. Generally,unless otherwise stated, these intensity thresholds are consistentbetween different sets of user interface figures.

An increase of intensity of the contact from an intensity below thelight press intensity threshold IT_(L) to an intensity between the lightpress intensity threshold IT_(L) and the deep press intensity thresholdIT_(D) is sometimes referred to as a “light press” input. An increase ofintensity of the contact from an intensity below the deep pressintensity threshold IT_(D) to an intensity above the deep pressintensity threshold IT_(D) is sometimes referred to as a “deep press”input. An increase of intensity of the contact from an intensity belowthe contact-detection intensity threshold IT₀ to an intensity betweenthe contact-detection intensity threshold IT₀ and the light pressintensity threshold IT_(L) is sometimes referred to as detecting thecontact on the touch-surface. A decrease of intensity of the contactfrom an intensity above the contact-detection intensity threshold IT₀ toan intensity below the contact intensity threshold IT₀ is sometimesreferred to as detecting liftoff of the contact from the touch-surface.In some embodiments IT₀ is zero. In some embodiments IT₀ is greater thanzero. In some illustrations a shaded circle or oval is used to representintensity of a contact on the touch-sensitive surface. In someillustrations a circle or oval without shading is used represent arespective contact on the touch-sensitive surface without specifying theintensity of the respective contact.

In some embodiments described herein, one or more operations areperformed in response to detecting a gesture that includes a respectivepress input or in response to detecting the respective press inputperformed with a respective contact (or a plurality of contacts), wherethe respective press input is detected based at least in part ondetecting an increase in intensity of the contact (or plurality ofcontacts) above a press-input intensity threshold. In some embodiments,the respective operation is performed in response to detecting theincrease in intensity of the respective contact above the press-inputintensity threshold (e.g., a “down stroke” of the respective pressinput). In some embodiments, the press input includes an increase inintensity of the respective contact above the press-input intensitythreshold and a subsequent decrease in intensity of the contact belowthe press-input intensity threshold, and the respective operation isperformed in response to detecting the subsequent decrease in intensityof the respective contact below the press-input threshold (e.g., an “upstroke” of the respective press input).

In some embodiments, the device employs intensity hysteresis to avoidaccidental inputs sometimes termed “jitter,” where the device defines orselects a hysteresis intensity threshold with a predefined relationshipto the press-input intensity threshold (e.g., the hysteresis intensitythreshold is X intensity units lower than the press-input intensitythreshold or the hysteresis intensity threshold is 75%, 90% or somereasonable proportion of the press-input intensity threshold). Thus, insome embodiments, the press input includes an increase in intensity ofthe respective contact above the press-input intensity threshold and asubsequent decrease in intensity of the contact below the hysteresisintensity threshold that corresponds to the press-input intensitythreshold, and the respective operation is performed in response todetecting the subsequent decrease in intensity of the respective contactbelow the hysteresis intensity threshold (e.g., an “up stroke” of therespective press input). Similarly, in some embodiments, the press inputis detected only when the device detects an increase in intensity of thecontact from an intensity at or below the hysteresis intensity thresholdto an intensity at or above the press-input intensity threshold and,optionally, a subsequent decrease in intensity of the contact to anintensity at or below the hysteresis intensity, and the respectiveoperation is performed in response to detecting the press input (e.g.,the increase in intensity of the contact or the decrease in intensity ofthe contact, depending on the circumstances).

For ease of explanation, the description of operations performed inresponse to a press input associated with a press-input intensitythreshold or in response to a gesture including the press input are,optionally, triggered in response to detecting either: an increase inintensity of a contact above the press-input intensity threshold, anincrease in intensity of a contact from an intensity below thehysteresis intensity threshold to an intensity above the press-inputintensity threshold, a decrease in intensity of the contact below thepress-input intensity threshold, and/or a decrease in intensity of thecontact below the hysteresis intensity threshold corresponding to thepress-input intensity threshold. Additionally, in examples where anoperation is described as being performed in response to detecting adecrease in intensity of a contact below the press-input intensitythreshold, the operation is, optionally, performed in response todetecting a decrease in intensity of the contact below a hysteresisintensity threshold corresponding to, and lower than, the press-inputintensity threshold.

User Interfaces and Associated Processes Selecting a Tactile OutputCorresponding to a Change in Intensity of a Contact

Many electronic devices have graphical user interfaces including one ormore user interface objects. When users attempt to perform operationsassociated with these user interface objects, these operations aresometimes successful and sometimes unsuccessful. For example, attemptingto move a user interface object to a region of a user interface thatdoes not accept user interface objects will be unsuccessful. In manyuser interfaces, there are one or more visual or audible cues as towhether or not the operation associated with the user interface objectwas successful. However, in some situations the user will miss a visualor audible cue as to whether or not an operation was successful (e.g.,because the user was not looking at the display and/or has the volume ofthe device turned down or turned off, or because the user was distractedwhen the cue was provided). A missed cue can result in the userattempting to repeat an operation that was successfully performed orproceeding to perform other operations without realizing that theattempted operation was not performed. Thus, it would be advantageous toprovide additional cues to the user to indicate whether or not anoperation was successful. In a touch-sensitive surface with anintegrated mechanical button, the sensation of reducing the intensity ofa contact on touch-sensitive surface is determined based on themechanism of the mechanical button and thus is the same (for the sameuser input) without regard to whether or not an operation associatedwith the contact was performed. In contrast, when the touch-sensitivesurface is associated with sensors for determining the intensity of thecontact with the touch-sensitive surface and a separate actuatorgenerates a software controlled tactile output on the touch-sensitivesurface, the tactile output generated after the user has attempted toperform an operation can be varied depending on whether or not theoperation was successfully performed (e.g., because the tactile outputsare decoupled from the intensity inputs). Providing such tactilefeedback as to whether or not an attempted operation has been performedimproves the machine-user interface by providing the user with timely,accurate feedback regarding performance of the operation.

FIGS. 5A-5W illustrate exemplary user interfaces for selecting a tactileoutput corresponding to a change in intensity of a contact in accordancewith some embodiments. The user interfaces in these are used toillustrate the processes described below, including the processes inFIGS. 6A-6B. FIGS. 5A-5W include intensity diagrams that show thecurrent intensity of the contact on the touch-sensitive surface relativeto a plurality of intensity thresholds including an object-selectionintensity threshold (e.g., “IT_(L)”) and an object-release threshold(e.g., “IT₁”. In some embodiments, the object-selection intensitythreshold is different from (e.g., higher than) the object-releaseintensity threshold. In some embodiments, the object-selection intensitythreshold is IT_(D) and the object-release intensity threshold is IT_(D)or an intensity threshold slightly below IT_(D).

FIG. 5A illustrates user interface 11700 (e.g., a desktop user interfaceor a drawing input area within a drawing or graphics application)displayed on display 450 (e.g., display 340) of a device (e.g., device300). One or more user interface objects 11702 are displayed in userinterface 11700. In FIG. 5A, user interface objects 11702-1 through11702-3 are displayed in user interface 11700. A user interface object11702 is, optionally one of, an application shortcut or launch icon, ashape or object within a drawing or graphics program, or other icon,widget, or object. One or more windows 11704 are, optionally, displayedin user interface 11700 as well. A window 11704 is, optionally, anapplication window corresponding to a respective application.

Cursor 11706 is also displayed in user interface 11700 on display 450.In some embodiments, cursor 11706 is a mouse pointer. Cursor 11706 is anexample of a focus selector. A user optionally positions cursor 11706 atany location in user interface 11700 by making a contact (for example, afinger contact or a stylus contact) on touch-sensitive surface 451(e.g., touchpad 355) of the device and moving the contact ontouch-sensitive surface 451 as desired. In response to the detection ofthe contact and movement of the contact on touch-sensitive surface 451,cursor 11706 is positioned at a position in user interface 11700 thatcorresponds to the current position of the contact on touch-sensitivesurface 451 and moves in accordance with movement of the contact ontouch-sensitive surface 451. In FIG. 5A, contact 11708 is detected at aposition on touch-sensitive surface 451, and cursor 11706 is positionedat a corresponding position in user interface 11700, over user interfaceobject 11702-2, as shown.

The device includes one or more sensors that detect the intensity ofcontacts with touch-sensitive surface 451. In FIG. 5A, the intensity ofcontact 11708 is detected to be below an object-selection threshold(e.g., “IT_(L)” in FIGS. 5A-5W). The intensity of contact 11708 belowthe object-selection threshold is represented by the empty background incontact 11708 as shown in FIG. 5A.

The intensity of contact 11708 is increased by, for example, the userapplying more pressure on touch-sensitive surface 451 with contact11708. The change in intensity of contact 11708 is detected by thecontact intensity sensors in the device. In response to the detection ofan increase in the intensity of contact 11708 above the object-selectionthreshold (with the intensity that is above the object-selectionthreshold represented by the densely dotted background in contact 11708as shown in FIG. 5B), a user interface object over which cursor 11706 ispositioned is selected. In FIG. 5B, cursor 11706 is positioned over userinterface object 11702-2, and thus user interface object 11702-2 isselected. User interface object 11706-2 is, optionally, visuallyhighlighted (for example, with a different color; with thicker borders,as shown in FIG. 5B) to indicate the selection. In some embodiments, atactile output indicative of the selection of user interface object11702-2 is generated on the touch-sensitive surface. The tactile outputindicative of the selection is, optionally, generated in accordance witha movement profile associated with selection of a user interface object.In some embodiments, the selection tactile output corresponds to atactile sensation that simulates a down-click of a mechanical button(for example, a click sensation of pressing a mouse button or a trackpadwith an integrated button).

While the intensity of contact 11708 remains above an object-releasethreshold (e.g., “IT₁” in FIGS. 5A-5W) and user interface object 11702-2remains selected, the user moves contact 11708 on touch-sensitivesurface 451. In response to detection of the movement of contact 11708,user interface object 11702-2, as well as cursor 11706, is moved acrossuser interface 11700 in accordance with the movement of contact 11708;user interface object 11702-2 is dragged across user interface 11700 inaccordance with the movement of contact 11708. For example, as shown inFIGS. 5C-5D, in response to the movement of contact 11708 in direction11710 on touch-sensitive surface 451, user interface object 11702-2moves in direction 11712 to another position in user interface 11700.The new position of user interface object 11702-2, as shown in FIG. 5D,is over “empty space” in user interface 11700, away from window 11704and other user interface objects 11702.

The object-release threshold is an intensity threshold that determineswhether a selected user interface object is released from selection. Insome embodiments, the object-release threshold is below theobject-selection threshold. In some other embodiments, theobject-release threshold is the same as the object-selection threshold.

While user interface object 11702-2 is located at the new position inuser interface 11700, as shown in FIG. 5D, the user reduces theintensity of contact 11708, such as by reducing the pressure ontouch-sensitive surface 451 with contact 11708 (including, for example,completely releasing contact 11708 from touch-sensitive surface 451). Asshown in FIG. 5E, the intensity of contact 11708 is reduced below theobject-release threshold, with the intensity below the object-releasethreshold represented by the sparsely dotted background in contact 11708and the intensity meter shown in FIG. 5E. In response to the reductionin intensity of contact 11708 below the object-release threshold, anattempt to relocate (or “drop”) user interface object 11702-2 at the newposition is made. The “empty space” in user interface 11700 is a validdrop location, as that empty space is not already occupied by a userinterface object 11702 or a window 11704, and thus the relocation ofuser interface object 11702-2 to the new position is successful. As aresult, user interface object 11702-2 is dropped at the new position inuser interface 11700 and de-selected (i.e., released from selection). Atactile output is generated on touch-sensitive surface 451, along withthe dropping of user interface object 502-2, in response to detection ofthe reduction in intensity of contact 11708 below the object-releasethreshold.

Returning to FIG. 5B, selected user interface object 11702-2 moves inresponse to detection of movement of contact 11708, as described above.FIGS. 5F-5G show user interface object 11702-2 moving in direction 11716in user interface 11700 to a new position that is over window 11704, inresponse to detection of movement of contact 11708 in direction 11714 ontouch-sensitive surface 451; user interface object 11702-2 is draggedacross user interface 11700 in accordance with the movement of contact11708.

While user interface object 11702-2 is located at the new position overwindow 11704, as shown in FIG. 5G, the user reduces the intensity ofcontact 11708, such as by reducing the pressure on touch-sensitivesurface 451 with contact 11708 (including, for example, lifting contact11708 off of touch-sensitive surface 451). As shown in FIG. 5H, theintensity of contact 11708 has been reduced below the object-releasethreshold. In response to the reduction in intensity of contact 11708below the object-release threshold, an attempt to relocate userinterface object 11702-2 at the new position is made (e.g., the positionof user interface object 11702-2 in FIG. 5G). The position over window11704 within user interface 11700 is an invalid drop location, as theposition is already occupied by window 11704, and thus the relocation ofuser interface object 11702-2 at the new position is unsuccessful. As aresult, user interface object 11702-2 is returned to its originallocation and de-selected. A tactile output that is different from thetactile output generated for the successful drop of user interfaceobject 11702-2, described above with reference to FIG. 5E, is generatedon touch-sensitive surface 451, along with the return of user interfaceobject 11702-2 to its original position, in response to detection of thereduction in intensity of contact 11708 below the object-releasethreshold.

Thus, after selection of user interface object 11702-2, movement ofcontact 11708 and a decrease in the intensity of contact 11708 below theobject-release threshold is performed by the user. In response to thedetection of the decrease in intensity below the object-releasethreshold, an attempt to drop user interface object 11702-2 at a newposition is made. Depending on whether the new position is a valid droptarget/location or an invalid drop target/location, the drop issuccessful (i.e., the drop is performed) or unsuccessful (i.e.,performance of the drop is not performed).

As described above, different tactile outputs are, optionally, generatedfor a successful drop of a user interface object (for example, asdescribed above with reference to FIG. 5E) and for an unsuccessful dropof a user interface object (for example, as described above withreference to FIG. 5H). In some embodiments, the tactile output for thesuccessful drop and the tactile output for the unsuccessful drop bothcorrespond to tactile sensations that simulate of an up-click of amechanical button (for example, releasing a clicked-and-held mousebutton). In some embodiments, the tactile outputs for a successful dropand an unsuccessful drop have different amplitudes but are otherwiseboth generated in accordance with the same movement profile. Forexample, the tactile output for the successful drop has a higheramplitude than, but otherwise have the same movement profile (e.g.,square waveform) as, the tactile output for the unsuccessful drop.

In some other embodiments, the tactile output for a successful drop andthe tactile output for an unsuccessful drop have different movementprofiles. For example, the tactile output for the successful drop is,optionally, generated in accordance with a sinusoidal movement profile,and the tactile output for the unsuccessful drop is, optionally,generated in accordance with a sawtooth waveform movement profile.

Returning to FIG. 5B, selected user interface object 11702-2 moves inresponse to detection of movement of contact 11708, as described above.FIGS. 5I-5K show user interface object 11702-2 moving, continuously, indirection 11722 and then direction 11724 in user interface 11700, inresponse to detection of continuous movement of contact 11708 indirection 11718 and then direction 11720, respectively, ontouch-sensitive surface 451. User interface object 11702-2 moves to aposition over window 11704 and then to “empty space” in user interface11700; user interface object 11702-2 is dragged across user interface11700 in accordance with the movement of contact 11708, over empty spaceand window 11704 at different times. Thus, during the movement, userinterface object 11702-2 moves over an invalid drop location for aperiod of time and over a valid drop location for another period oftime.

As user interface object 11702-2 is moving, while user interface object11702-2 is over window 11704, as shown in FIG. 5J, a tactile outputassociated with an invalid drop location is, optionally, generated ontouch-sensitive surface 451. The tactile output alerts the user that thecurrent position of the user interface object 11702-2 is an invalid droplocation.

As user interface object 11702-2 continues to move, while user interfaceobject 11702-2 is over empty space in user interface 11700, as shown inFIG. 5K, a tactile output associated with a valid drop location is,optionally, generated on touch-sensitive surface 451. The tactile outputalerts the user that the current position of the user interface object11702-2 is a valid drop location. The tactile output associated with avalid drop location is different from the tactile output associated withan invalid drop location. For example, the valid drop location tactileoutput has a higher amplitude and/or different movement profile from theinvalid drop location tactile output. In some embodiments, the tactileoutput associated with a valid drop target/location is generatedaccording to the same movement profile and amplitude as a tactile outputassociated with a successful drop. Similarly, the tactile outputassociated with an invalid drop target/location is generated accordingto the same movement profile and amplitude as a tactile outputassociated with an unsuccessful drop. For example, the touch-sensitivesurface optionally provides a high frequency periodic tactile output(e.g., a slight buzzing) while user interface object 11702-2 is over aninvalid drop target and either does not provide any tactile output orprovides a low frequency periodic tactile output (e.g., a periodic ping)while user interface object 11702-2 is over a valid drop target.

When the intensity of contact 11708 is reduced below the object-releasethreshold while user interface object 11702-2 is over empty space inuser interface 11700, as shown in FIG. 5L, user interface object 11702-2is dropped successfully at its new position.

It should be appreciated that the criteria for a valid droptarget/location and an invalid drop target/location described above(whether a location is already occupied by a user interface object 11702or window 11704) are merely exemplary, and other criteria are,optionally, employed in other embodiments, implementations, or fordifferent categories of user interface objects or for differentoperations within an embodiment or implementation. For example, droppingan application shortcut or launch icon at a position over anotherapplication shortcut/launch icon or over an application window isinvalid, while dropping a shape within a drawing program at a positionover another shape is valid. As another example, dropping an applicationshortcut/launch icon at a position over another applicationshortcut/launch icon is valid if the operation includes swapping thelocations of the application shortcuts/launch icons affected.

As described above, tactile outputs are, optionally, generated for aselection of a user interface object, a valid drop, an invalid drop, avalid drop location, and an invalid drop location. FIGS. 5M-5Oillustrate example waveforms of movement profiles for generating thesetactile outputs. FIG. 5M illustrates a sawtooth waveform. FIG. 5Nillustrates a square waveform, and FIG. 5O illustrates a square waveformthat has a lower amplitude than the square waveform of FIG. 5N. Thesawtooth movement profile in FIG. 5M is, optionally, associated withselection of a user interface object; the tactile output generated forselection of a user interface object is, optionally, generated inaccordance with the sawtooth movement profile. The high-amplitude squaremovement profile in FIG. 5N is, optionally, associated with a successfuldrop (or a valid drop target/location); the tactile output generated fora successful drop or valid drop target/location is, optionally,generated in accordance with a high-amplitude square movement profile.The low-amplitude square movement profile in FIG. 5O is, optionally,associated with an unsuccessful drop (or an invalid droptarget/location); the tactile output generated for an unsuccessful dropor invalid drop target/location is, optionally, generated in accordancewith a low-amplitude square movement profile.

FIGS. 5P-5W illustrate an example of the user interfaces describedabove, with reference to FIGS. 5A-5O, implemented on a device (e.g.,device 100) with a touch-sensitive display 112. FIG. 5P illustrates userinterface 11736 (e.g., a home menu or screen interface, a desktop userinterface, a drawing input area within a drawing or graphicsapplication) displayed on touch-sensitive display 112 of a device. Oneor more user interface objects 11732 are, optionally displayed in userinterface 11736. In FIG. 5P, user interface objects 11732-1 through11732-3 are displayed in user interface 11736. A user interface object11732 is, for example, an application shortcut or launch icon, a shapeor object within a drawing or graphics program, or other icon, widget,or object. One or more windows 11734 are, optionally, displayed in userinterface 11736 as well. A window 11734 is, for example, an applicationwindow corresponding to a respective application. Contact 11738 isdetected on touch-sensitive display at a location over user interfaceobject 11732-2.

The device includes one or more sensors that detect the intensity ofcontacts with touch-sensitive display 112. In FIG. 5P, the intensity ofcontact 11738 is detected to be below an object-selection threshold. Theintensity of contact 11738 below the object-selection threshold isrepresented by the empty background in contact 11738 as shown in FIG.5P.

The intensity of contact 11738 is increased by, for example, the userapplying more pressure on touch-sensitive display 112 with contact11738. The change in intensity of contact 11738 is detected by thecontact intensity sensors in the device. In response to the detection ofan increase in the intensity of contact 11738 above the object-selectionthreshold (with the intensity that is above the object-selectionthreshold represented by the densely dotted background in contact 11738and the intensity meter shown in FIG. 5Q), a user interface object overwhich contact 11738 is positioned is selected. In FIG. 5Q, contact 11738is positioned over user interface object 11732-2, and thus userinterface object 11732-2 is selected. User interface object 11736-2 is,optionally, visually highlighted (for example, with a different color;with thicker borders, as shown in FIG. 5Q) to indicate the selection. Insome embodiments, a tactile output indicative of the selection of userinterface object 11732-2 is generated on touch-sensitive display 112.The tactile output indicative of the selection is, optionally, generatedin accordance with a movement profile associated with selection of auser interface object. In some embodiments, the selection tactile outputcorresponds to a tactile sensation that simulates a down-click of amechanical button (for example, a click sensation of a pressing mousebutton).

While the intensity of contact 11738 remains above an object-releasethreshold and user interface object 11732-2 remains selected, the usermoves contact 11738 on touch-sensitive display 112. In response todetection of the movement of contact 11738, user interface object11732-2 is moved across user interface 11736 in accordance with themovement of contact 11738; user interface object 11732-2 is draggedacross user interface 11736 in accordance with the movement of contact11738. For example, as shown in FIGS. 5R-5S, in response to movement ofcontact 11738 in direction 11740 on touch-sensitive display 112, userinterface object 11732-2 moves in the same direction as contact 11738 toanother position in user interface 11736. The new position of userinterface object 11732-2, as shown in FIG. 5S, is over “empty space” inuser interface 11736, away from window 11734 and other user interfaceobjects 11732-1 and 11732-3.

While user interface object 11732-2 is located at the new position inuser interface 11736, as shown in FIG. 5S, the user reduces theintensity of contact 11738, such as by reducing the pressure ontouch-sensitive display 112 with contact 11738 (including, for example,lifting contact 11738 off of touch-sensitive display 112). As shown inFIG. 5T, the intensity of contact 11738 is reduced below theobject-release threshold, with the intensity below the object-releasethreshold represented by the sparsely dotted background in contact 11738and the intensity meter. In response to the reduction in intensity ofcontact 11738 below the object-release threshold, an attempt to relocate(or “drop”) user interface object 11732-2 at the new position is made.The “empty space” in user interface 11736 is a valid drop location, asthat empty space is not already occupied by a user interface object11732 or a window 11734, and thus the relocation of user interfaceobject 11732-2 to the new position is successful. As a result, userinterface object 11732-2 is dropped at the new position in userinterface 11736 and de-selected (i.e., released from selection). Atactile output is generated on touch-sensitive display 112, along withthe dropping of user interface object 532-2, in response to detection ofthe reduction in intensity of contact 11738 below the object-releasethreshold.

Returning to FIG. 5Q, selected user interface object 11732-2 moves inresponse to detection of movement of contact 11738, as described above.FIGS. 5U-5V show user interface object 11732-2 moving in direction 11742in user interface 11736 to a new position that is over window 11734, inresponse to detection of movement of contact 11738 in direction 11742 ontouch-sensitive display 112; user interface object 11732-2 is draggedacross user interface 11736 in accordance with the movement of contact11738.

While user interface object 11732-2 is located at the new position overwindow 11734, as shown in FIG. 5V, the user reduces the intensity ofcontact 11738, such as by reducing the pressure on touch-sensitivedisplay 112 with contact 11738 (including, for example, completelyreleasing contact 11738 from touch-sensitive display 112). As shown inFIG. 5W, the intensity of contact 11738 has been reduced below theobject-release threshold. In response to the reduction in intensity ofcontact 11738 below the object-release threshold, an attempt to relocateuser interface object 11732-2 at the new position is made. The positionover window 11734 within user interface 11736 is an invalid droplocation, as the position is already occupied by window 11734, and thusthe relocation of user interface object 11732-2 at the new position isunsuccessful. As a result, user interface object 11732-2 is returned toits original location and de-selected. A tactile output that isdifferent from the tactile output generated for the successful drop ofuser interface object 11732-2, described above with reference to FIG.5T, is generated on touch-sensitive display 112, along with the returnof user interface object 11732-2 to its original position, in responseto detection of the reduction in intensity of contact 11738 below theobject-release threshold.

FIGS. 6A-6B are flow diagrams illustrating a method 11800 of selecting atactile output corresponding to a change in intensity of a contact inaccordance with some embodiments. The method 11800 is performed at anelectronic device (e.g., device 300, FIG. 3, or portable multifunctiondevice 100, FIG. 1A) with a display, a touch-sensitive surface, and oneor more sensors to detect intensity of contacts with the touch-sensitivesurface. In some embodiments, the display is a touch screen display andthe touch-sensitive surface is on the display. In some embodiments, thedisplay is separate from the touch-sensitive surface. Some operations inmethod 11800 are, optionally, combined and/or the order of someoperations is, optionally, changed.

As described below, the method 11800 provides an intuitive way torelocate a user interface object. The method reduces the cognitiveburden on a user when relocating user interface objects, therebycreating a more efficient human-machine interface. For battery-operatedelectronic devices, enabling a user to relocate a user interface objectfaster and more efficiently conserves power and increases the timebetween battery charges.

The device displays (11802) a user interface object on the display. FIG.5A, for example, shows user interface objects 11702-1 through 11702-3displayed on display 450. As another example, FIG. 5P shows userinterface objects 11732-1 through 11732-3 displayed on touch-sensitivedisplay 112.

The device detects (11804), on the touch-sensitive surface, a contact(e.g., a finger contact or a stylus contact) having an intensity abovean object-selection threshold (e.g., “IT_(L)”). The device can, usingthe one or more sensors, detect an intensity of a contact on thetouch-sensitive surface (e.g., touchpad 355). In FIG. 5B, for example,contact 11708 which has an intensity greater than an object-selectionthreshold, is detected. Similarly, in FIG. 5Q, contact 11738, which hasan intensity greater than an object-selection threshold, is detected.

In some embodiments, prior to detecting movement of the contact acrossthe touch-sensitive surface (11806), in response to detecting anincrease in intensity of the contact above the object-selectionthreshold, the device generates (11808) a selection tactile output onthe touch-sensitive surface indicative of the selection. The contactthat is detected as having an intensity above the object-selectionthreshold has the intensity above the object-selection threshold as aresult of an increase in intensity of the contact from below theobject-selection threshold to above the object-selection threshold. Whenthe increase in intensity above the object-selection threshold isdetected prior to movement of the contact across the touch-sensitivesurface, a user interface object is selected and a selection tactileoutput is generated in response.

For example, in FIG. 5A, contact 11708 on touch-sensitive surface 451has an intensity below the object-selection threshold, and a focusselector (e.g., cursor 11706) is positioned over user interface object11702-2 in accordance with the position of contact 11708 ontouch-sensitive surface 451. When, prior to movement of contact 11708across touch-sensitive surface 451, the intensity of contact 11708 isdetected to have increased above the object-selection threshold, asshown in FIG. 5B, user interface object 11702-2 is selected and atactile output associated with selection of a user interface object isgenerated on touch-sensitive surface 451. The tactile output indicatesto the user that user interface object 502-2 has been selected.Similarly, a tactile output is generated in response to detection of theincrease in the intensity of contact 11738 above the object-selectionthreshold.

The device detects (11810) movement of the contact across thetouch-sensitive surface, the movement corresponding to a preliminaryportion of a gesture for performing an operation corresponding to theuser interface object. For example, the movement is part of an operationto relocate an icon representing a file stored on the device, which willbe completed if the icon is moved to a valid drop target and droppedonto the valid drop target (e.g., in response to detecting a liftoff ofthe contact or a reduction in intensity/pressure of the contact on thetouch sensitive surface below an object-release threshold, such as “IT₁”or “IT_(L)”). For example, in FIGS. 5C-5D, contact 11708 moves indirection 11710 on touch-sensitive surface 451, and the movement isdetected by the device. In FIGS. 5F-5G, contact 11708 moves in direction11714 on touch-sensitive surface 451, and the movement is detected bythe device. In FIGS. 5I-5K, contact 11708 moves in direction 11718 andthen 11720 on touch-sensitive surface 451. In response to the detectionof the respective movement of contact 11708, user interface object11702-2 is moved in user interface 11700 in accordance with the detectedmovement of contact 11708. The movement is part of a gesture to relocateuser interface object 11702-2 in user interface 11700. As anotherexample, in FIGS. 5Q-5R, movement of contact 11738 in direction 11740 isdetected, and in FIGS. 5U-5V, movement of contact 11738 in direction11742 is detected.

In some embodiments, for a first time period during the gesture, theuser interface object is over an invalid drop target, and for a secondtime period during the gesture, the user interface object is over avalid drop target (11812). The device, during the first period of time,generates (11814) an invalid-drop-target tactile output on thetouch-sensitive surface. The device, during the second period of time,generates (11816) a valid-drop-target tactile output on thetouch-sensitive surface, where the invalid-drop-target tactile output isdifferent from the valid-drop-target tactile output. In some situations,when a user interface object is moved, the user interface object is overa valid drop target or location for a time period and is over an invaliddrop target or location for another time period (e.g., as illustrated inFIGS. 5I-5K). During the time period when the user interface object isover a valid drop target or location, a tactile output is generated ontouch-sensitive surface 451. During the time period when the userinterface object is over an invalid drop target or location, a differenttactile output is generated on touch-sensitive surface 451.

For example, in FIGS. 5I-5K, user interface object 11702-2 is moved inaccordance with the movement of contact 11708 on touch-sensitive surface451. In FIG. 5J, user interface object 11702-2 moves over window 11704,an invalid drop target. In FIG. 5K, user interface object 11702-2 movesover empty space in user interface 11700, a valid drop target. Duringthe period when user interface object 11702-2 is moving over window11704, a tactile output is generated. During the period when userinterface object 11702-2 is moving over empty space in user interface11700, a tactile output different from that generated for the periodwhen user interface object 11702-2 is moving over window 11704 isgenerated. The tactile outputs is different with respect to amplitudeand/or movement profile. For example, the touch-sensitive surfaceoptionally provides a high frequency periodic tactile output (e.g., aslight buzzing) while user interface object 11702-2 is over an invaliddrop target and either does not provide any tactile output or provides alow frequency periodic tactile output (e.g., a periodic ping) while userinterface object 11702-2 is over a valid drop target.

The device detects (11818) a reduction in intensity of the contact belowan object-release threshold. When user interface object 11702-2 is movedto the target location for the drop, the user reduces the intensity ofcontact 11708 below the object-release threshold (e.g., reducingintensity of the contact while maintaining the contact or lifting thecontact off of the touch-sensitive surface) to make the drop attempt, asshown in FIG. 5E, 5H, or 5L, for example. As another example, when userobject 11732-2 is moved to the target location for the drop, the userreduces the intensity of contact 11738 below the object-releasethreshold (e.g., reducing intensity of the contact while maintaining thecontact or lifting the contact off of the touch-sensitive surface) tomake the drop attempt, as shown in FIG. 5T or 5W.

In response to detecting the reduction in intensity below theobject-release threshold (11820), in accordance with a determinationthat the movement meets predefined operation-performance criteria(11822), the device performs (11824) the operation and generates (11826)a first tactile output on the touch-sensitive surface. In accordancewith a determination that the movement does not meet the predefinedoperation-performance criteria (11828), the device forgoes (11830)performance of the operation and generates (11832) a second tactileoutput on the touch-sensitive surface, where the second tactile outputis different from the first tactile output. For example, in response tothe reduction in intensity of contact 11708 or 11738 below theobject-release threshold (e.g., a reduction in intensity of the contactwhile maintaining the contact or lifting the contact off of thetouch-sensitive surface), an attempt to drop user interface object11702-2 or 11732-2, respectively is made. Whether the drop is performed(e.g., if the drop is successful or not) depends on whether one or morepredefined operation-performance criteria are satisfied. In someembodiments, for a drop operation, a criterion for operation performanceis whether the drop target/location is valid. If user interface object11702-2 or 11732-2 is over a valid drop target (and thus a determinationis made that the predefined operation-performance criteria for a dropare satisfied), such as empty space in user interface 11700 or 11736,the drop is performed, as shown in FIG. 5E, 5L, or 5T, respectively, anda tactile output associated with a successful drop is generated ontouch-sensitive surface 451 or touch-sensitive display 112. If userinterface object 11702-2 or 11732-2 is over an invalid drop target (andthus a determination is made that the predefined operation-performancecriteria for a drop are not satisfied), such as window 11704 or 11734,the drop is not performed, as shown in FIG. 5H or 5W, respectively, anda tactile output associated with an unsuccessful drop is generated ontouch-sensitive surface 451 or touch-sensitive display 112.

In some embodiments, the operation is an object drop operation (e.g., afile move operation such as dragging an icon representing a file to anew location in a file manager user interface), the movement correspondsto movement of the user interface object to a respective location in theuser interface, the movement meets the predefined operation-performancecriteria when the respective location is a valid drop location, and themovement does not meet the predefined operation-performance criteriawhen the respective location is an invalid drop location (11834). Asdescribed above, the movement of contact 11708 is, optionally, part of agesture for performing a drag and drop operation in user interfaceobject 11702-2 that corresponds to movement of user interface object11702-2 to a new location in user interface 11700. When user interfaceobject 11702-2 is moved to a valid drop target/location, the movement inthe gesture is considered to satisfy the criteria for performing a dropoperation, and the drop is performed, as shown in FIG. 5E or 5L, forexample. On the other hand, when user interface object 11702-2 is movedto an invalid drop target/location, the movement in the gesture isconsidered to not satisfy the criteria for performing a drop operation,and the drop is not performed, as shown in FIG. 5H, for example.Similarly, movement of contact 11738 is, optionally, part of a gesturefor performing a drag and drop operation in user interface object11732-2 that corresponds to movement of user interface object 11732-2 toa new location in user interface 11736. When user interface object11732-2 is moved to a valid drop target/location, the movement in thegesture is considered to satisfy the criteria for performing a dropoperation; the drop is performed, as shown in FIG. 5T, for example. Onthe other hand, when user interface object 11732-2 is moved to aninvalid drop target/location, the movement in the gesture is consideredto not satisfy the criteria for performing a drop operation; the drop isnot performed, as shown in FIG. 5W, for example.

In some embodiments, the first tactile output is generated by movementof the touch-sensitive surface that includes a first dominant movementcomponent (e.g., movement corresponding to the initial impulse, ignoringany unintended resonance), the second tactile output is generated bymovement of the touch-sensitive surface that includes a second dominantmovement component, and the first dominant movement component and thesecond dominant movement component have a same movement profile (e.g.,same waveform shape such as square, sine, squine, sawtooth or triangle;and/or approximately the same width/period) and different amplitudes(11836). The tactile output for a successful drop and the tactile outputfor an unsuccessful drop both have respective dominant movementcomponents that have respective movement profiles (for example, themovement profiles depicted in FIGS. 5N and 5O, respectively). The twotactile outputs optionally have the same movement profile but differentamplitudes, as shown in FIGS. 5N and 5O, for example. Thus, in someembodiments, the tactile outputs for a successful drop and anunsuccessful drop optionally differ in amplitude rather than in themovement profile; one sensation is a more intense version of the othersensation.

In some embodiments, the selection tactile output corresponds to atactile sensation that simulates a down-click of a mechanical button,the first tactile output corresponds to a first tactile sensation thatsimulates an up-click of the mechanical button, and the second tactileoutput corresponds to a second tactile sensation that simulates anup-click of the mechanical button, where the second tactile sensationfeels different (e.g., to a user of the device) from the first tactilesensation (11838). The selection tactile output corresponds to asimulation of, for example, a click-and-hold of a mouse button on mouse350 or trackpad of device 300. The first tactile output corresponds to atactile sensation that simulates a release of the mouse button (ortrackpad button). The second tactile output corresponds to a tactilesensation that simulates the release of the mouse button (or trackpadbutton) in a way that is different from the first tactile output. Thefirst and second tactile sensations optionally simulate the mouse buttonrelease differently by using, for example, different amplitudes and/ordifferent movement profiles.

It should be understood that the particular order in which theoperations in FIGS. 6A-6B have been described is merely exemplary and isnot intended to indicate that the described order is the only order inwhich the operations could be performed. One of ordinary skill in theart would recognize various ways to reorder the operations describedherein. Additionally, it should be noted that details of other processesdescribed herein with respect to other methods described herein (e.g.,those listed in the fifth paragraph of the Description of Embodiments)are also applicable in an analogous manner to method 11800 describedabove with respect to FIGS. 6A-6B. For example, the contacts, userinterface objects, tactile outputs, intensity thresholds, and focusselectors described above with reference to method 11800 optionally haveone or more of the characteristics of the contacts, gestures, userinterface objects, tactile outputs, intensity thresholds, and focusselectors described herein with reference to other methods describedherein (e.g., those listed in the fifth paragraph of the Description ofEmbodiments). For brevity, these details are not repeated here.

In accordance with some embodiments, FIG. 7 shows a functional blockdiagram of an electronic device 11900 configured in accordance with theprinciples of the various described embodiments. The functional blocksof the device are, optionally, implemented by hardware, software, or acombination of hardware and software to carry out the principles of thevarious described embodiments. It is understood by persons of skill inthe art that the functional blocks described in FIG. 7 are, optionally,combined or separated into sub-blocks to implement the principles of thevarious described embodiments. Therefore, the description hereinoptionally supports any possible combination or separation or furtherdefinition of the functional blocks described herein. As shown in FIG.7, an electronic device 11900 includes a display unit 11902 configuredto display a user interface object, a touch-sensitive surface unit 11904configured to receive contacts, one or more sensor units 11905configured to detect intensity of contacts with the touch-sensitivesurface unit 11904, and a processing unit 11906 coupled to the displayunit 11902, the touch-sensitive surface unit 11904, and the sensor units11905. In some embodiments, the processing unit 11906 includes adetecting unit 11908, a performing unit 11910, and a generating unit11912.

The processing unit 11906 configured to: detect, on the touch-sensitivesurface unit 11904, a contact having an intensity above anobject-selection threshold (e.g., with the detecting unit 11908); detectmovement of the contact across the touch-sensitive surface unit 11904,the movement corresponding to a preliminary portion of a gesture forperforming an operation corresponding to the user interface object(e.g., with the detecting unit 11908); detect a reduction in intensityof the contact below an object-release threshold (e.g., with thedetecting unit 11908); and in response to detecting the reduction inintensity below the object-release threshold: in accordance with adetermination that the movement meets predefined operation-performancecriteria: perform the operation (e.g., with the performing unit 11910);and generate a first tactile output on the touch-sensitive surface unit11904 (e.g., with the generating unit 11912); and in accordance with adetermination that the movement does not meet the predefinedoperation-performance criteria: forgo performance of the operation(e.g., with the performing unit 11910); and generate a second tactileoutput on the touch-sensitive surface unit 11904, wherein the secondtactile output is different from the first tactile output (e.g., withthe generating unit 11912).

In some embodiments, the operation is an object drop operation, themovement corresponds to movement of the user interface object to arespective location in the user interface, the movement meets thepredefined operation-performance criteria when the respective locationis a valid drop location, and the movement does not meet the predefinedoperation-performance criteria when the respective location is aninvalid drop location.

In some embodiments, the processing unit 11906 is configured to, priorto detecting movement of the contact across the touch-sensitive surfaceunit 11904: in response to detecting an increase in intensity of thecontact above the object-selection threshold, generate a selectiontactile output on the touch-sensitive surface unit 11904 indicative ofthe selection (e.g., with the generating unit 11912).

In some embodiments, the selection tactile output corresponds to atactile sensation that simulates a down-click of a mechanical button,the first tactile output corresponds to a first tactile sensation thatsimulates an up-click of the mechanical button, and the second tactileoutput corresponds to a second tactile sensation that simulates anup-click of the mechanical button, where the second tactile sensationfeels different from the first tactile sensation.

In some embodiments, the first tactile output is generated by movementof the touch-sensitive surface unit 11904 that includes a first dominantmovement component, the second tactile output is generated by movementof the touch-sensitive surface unit 11904 that includes a seconddominant movement component, and the first dominant movement componentand the second dominant movement component have a same movement profileand different amplitudes.

In some embodiments, for a first time period during the gesture, theuser interface object is over an invalid drop target, for a second timeperiod during the gesture, the user interface object is over a validdrop target, and the processing unit 11906 is configured to: during thefirst period of time generate an invalid-drop-target tactile output onthe touch-sensitive surface unit 11904 (e.g., with the generating unit11912), and during the second period of time generate avalid-drop-target tactile output on the touch-sensitive surface unit11904, where the invalid-drop-target tactile output is different fromthe valid-drop-target tactile output (e.g., with the generating unit11912).

The operations in the information processing methods described aboveare, optionally implemented by running one or more functional modules ininformation processing apparatus such as general purpose processors(e.g., as described above with respect to FIGS. 1A and 3) or applicationspecific chips.

The operations described above with reference to FIGS. 6A-6B are,optionally, implemented by components depicted in FIG. 1A-1B or FIG. 7.For example, detection operations 11804, 11810, and 11818, performingoperation 11824, forgoing operation 11830, and generating operations11826 and 11832 are, optionally, implemented by event sorter 170, eventrecognizer 180, and event handler 190. Event monitor 171 in event sorter170 detects a contact on touch-sensitive display 112, and eventdispatcher module 174 delivers the event information to application136-1. A respective event recognizer 180 of application 136-1 comparesthe event information to respective event definitions 186, anddetermines whether a first contact at a first location on thetouch-sensitive surface corresponds to a predefined event or sub-event,such as selection of an object on a user interface. When a respectivepredefined event or sub-event is detected, event recognizer 180activates an event handler 190 associated with the detection of theevent or sub-event. Event handler 190 optionally utilizes or calls dataupdater 176 or object updater 177 to update the application internalstate 192. In some embodiments, event handler 190 accesses a respectiveGUI updater 178 to update what is displayed by the application.Similarly, it would be clear to a person having ordinary skill in theart how other processes can be implemented based on the componentsdepicted in FIGS. 1A-1B, 3.

Performing Operations Based on Modified Inputs

Many electronic devices include a mouse or similar input device thatprovides left-click functionality and right-click functionality foractivating different operations. As devices economize on the number ofbuttons and input devices, the left-click functionality and right-clickfunctionality is, optionally, invoked using one input device, such as atrackpad. In existing methods, when either functionality is invokedusing the one input device, the user is not given sufficient feedbackindicating whether the activated operation was an operation notassociated with a modifier input (e.g., a left-click operation) or anoperation associated with a modifier input (e.g., a right-clickoperation). The embodiments below improve on the existing methods byproviding different tactile output when device detects an input while amodifier input is detected than when the device detects a similar inputwhile a modifier input is not detected. Thus, the device provides theuser with tactile feedback indicating whether or not the modifier inputwas detected instead of or in addition to any visual or audible feedbackindicating that the modifier input was detected. This additional (oralternative) feedback enables the user to operate the device morequickly and efficiently, thereby creating a more efficient human-machineinterface.

FIGS. 8A-8V illustrate exemplary user interfaces for providing feedbackcorresponding to modifier inputs in accordance with some embodiments.The user interfaces in these figures are used to illustrate theprocesses described below, including the processes in FIGS. 9A-9B. FIGS.8A-8V include intensity diagrams that show the current intensity of thecontact on the touch-sensitive surface relative to a plurality ofintensity thresholds including a first activation threshold (e.g.,“IT_(L)”) and a second activation threshold (e.g., “IT₁” or “IT_(L)”).In some embodiments, operations similar to those described below withreference to “IT_(L)” are performed with reference to a differentintensity threshold (e.g., “IT_(D)”).

FIG. 8A illustrates user interface 12000 (e.g., a desktop userinterface) displayed on display 450 (e.g., display 340) of a device(e.g., device 300). One or more user interface objects 12002 are,optionally, displayed on user interface 12000. In FIG. 8A, userinterface objects 12002-1 through 12002-3 are displayed on userinterface 12000. A user interface object 12002 is, optionally, forexample, an application shortcut or launch icon.

Cursor 12004 is also displayed on user interface 12000. In someembodiments, cursor 12004 is a mouse pointer. Cursor 12004 is an exampleof a focus selector. In FIG. 8A, cursor 12004 is displayed over userinterface object 12002-2.

The device includes one or more sensors that detect the intensity ofcontacts with touch-sensitive surface 451 (e.g., touchpad 355) of thedevice. In FIG. 8A, the intensity of contact 12006 is detected to bebelow a first activation threshold (e.g., “IT_(L)”).

The intensity of a contact (e.g., contact 12006) on touch-sensitivesurface 451 is, optionally, increased or decreased by, for example, theuser increasing or decreasing, respectively, the pressure ontouch-sensitive surface 451 with the contact. The change in intensity ofthe contact is, optionally, detected by the sensors in the device.

In FIG. 8B, the device detects an increase in intensity of contact 12006above the first activation threshold. In some situations, afterdetecting the increase in intensity of contact 12006, a decrease in theintensity of contact 12006 (e.g., a liftoff of contact 12006 fromtouch-sensitive surface 451) below a second activation threshold (e.g.,“IT₁”) is be detected by the intensity sensors in the device. In someembodiments, the first activation threshold and the second activationthreshold are different and the second activation threshold is lowerthan the first activation threshold (e.g., the first activationthreshold is “IT_(L)” and the second activation threshold is “IT₁” or,alternatively, “IT₀”). In some other embodiments, the first activationthreshold and the second activation threshold are the same (e.g., thefirst activation threshold is “IT_(L)” and the second activationthreshold is also “IT_(L)”).

In response to the detection of the decrease in intensity of contact12006 below the second activation threshold (e.g., “IT₁”), afterdetection of the increase in the intensity of contact 12006 above thefirst activation threshold (e.g., “IT_(L)”), one or more operationsassociated with user interface object 12002-2, over which cursor 12004is positioned, are, optionally, performed. In some embodiments, theoperation(s) include displaying a new application window associated withuser interface object 12002-2. For example, if user interface object12002-2 is an icon (e.g., an application launch or shortcut icon)corresponding to an application, window 12008 for the correspondingapplication is, optionally, displayed on user interface 12000, as shownin FIG. 8C.

In some embodiments, user interface object 12002-2 is visuallyhighlighted in response to the detection of the increase then decreasein intensity, or in response to the detection of the increase inintensity. Examples of visual highlighting include a different color orthicker borders (as shown in FIG. 8C).

Additionally, in response to detection of the decrease in the intensityof contact 12006 below the second activation threshold, after detectionof the increase in the intensity of contact 12006 above the firstactivation threshold, a tactile output is generated on touch-sensitivesurface 451. The tactile output is, optionally, generated in accordancewith a movement profile (e.g., movement profiles illustrated in FIGS.8P-8Q) and/or an amplitude.

Returning to FIG. 8A, the intensity of contact 12006 is, optionally,increased above the first activation threshold concurrently with thedetection of a modifier input. An example of a modifier input is a keypress of a key (e.g., on a keyboard) assigned to be a modifier key. Akey on keyboard 12011 (e.g., keyboard 350) is, optionally, pre-assignedto be a modifier key (e.g., as a default) or assigned by a user. FIG. 8Dshows key press 12012 on key 12010 of keyboard 12011 concurrent withdetection of an increase in the intensity of contact 12006 above thefirst activation threshold. After concurrent detection of the increasein the intensity of contact 12006 above the first activation threshold(e.g., “IT_(L)”) and of key press 12012 on key 12010, the intensity ofcontact 12006 is decreased below a second activation threshold (e.g.,“IT₁”), as shown in FIG. 8E (at which point continued pressing of key12010 is optional). In response to detecting the decrease in theintensity of contact 12006 below the second activation threshold, afterconcurrent detection of the increase in the intensity of contact 12006above the first activation threshold and key press 12012 of key 12010,an operation different from that performed when no modifier input isdetected is performed. For example, FIG. 8E shows context menu 12014displayed on user interface 12000 near cursor 12004 in response to thedetection of the decrease in the intensity of contact 12006 below thesecond activation threshold, after concurrent detection of the increasein the intensity of contact 12006 above the first activation thresholdand press 12012 of key 12010. The operation of displaying context menu12014 is different from the operation of displaying application window12008 (FIG. 8C) that was performed in response to detection of thedecrease in the intensity of contact 12006 below the second activationthreshold, after detection of the increase in the intensity of contact12006 above the first activation threshold without concurrent detectionof a press of key 12010. Context menu 12014 includes menu optionsassociated with user interface object 12002-2, over which cursor 12004is positioned, such as “rename,” “properties,” and so on. The menuoptions include options for performing operations on or with respect touser interface object 12002-2.

Another example of a modifier input is an additional contact that isdetected on touch-sensitive surface 451 concurrently with detection ofcontact 12006. FIG. 8F shows contact 12016 detected on touch-sensitivesurface 451 concurrently with the detection of an increase in theintensity of contact 12006 above the first activation threshold (e.g.,“IT_(L)”) and a subsequent decrease in the intensity of contact 12006below the second activation threshold (e.g., “IT₁”), as shown in FIG.8G. In response to detection of the decrease in the intensity of contact12006 below the second activation threshold, after concurrent detectionof the increase in the intensity of contact 12006 above the firstactivation threshold and contact 12016, context menu 12014 is displayedon user interface 12000, as shown in FIG. 8G.

A further example of a modifier input is detection of the contact 12006at a specific area on touch-sensitive surface 451, as opposed to anarbitrary location on touch-sensitive surface 451 outside of thespecific area on the touch-sensitive surface. FIG. 8H shows contact12006 detected in area 12018 on touch-sensitive surface 451, at anintensity below the first activation threshold. An increase in theintensity of contact 12006 in area 12018 above the first activationthreshold (e.g., “IT_(L)”) is detected, as shown in FIG. 8I. Then, adecrease in the intensity of contact 12006 in area 12018 below thesecond activation threshold (e.g., “IT_(L)”) is detected, as shown inFIG. 8J. In response to detection of the decrease in the intensity ofcontact 12006 in area 12018 below the second activation threshold, afterdetection of the increase in the intensity of contact 12006 in area12018 above the first activation threshold, context menu 12014 isdisplayed on user interface 12000, as shown in FIG. 8J. Here, detectionof contact 12006 in a defined area (e.g., area 12018) on touch-sensitivesurface 451 modified the input of contact 12006.

In some embodiments, the defined area (e.g., area 12018) ontouch-sensitive surface 451 for modifying the input is predefined, or itis, optionally, defined by the user (e.g., from a predefined set ofchoices). Further, it should be appreciated that the size and locationof area 12018 as shown in FIGS. 8H-8J are merely an illustrativeexample, and other sizes and/or locations for area 12018 are possible.

Additionally, in response to detection of the decrease in the intensityof contact 12006 below the second activation threshold (e.g., “IT₁”),after concurrent detection of the increase in the intensity of contact12006 above the first activation threshold (e.g., “IT_(L)”) and amodifier input (e.g., press 12012 of modifier key 12010, contact 12016,detecting contact 12006 in area 12018 on touch-sensitive surface 451), atactile output (e.g., a “modifier-active tactile output”) is generatedon touch-sensitive surface 451. This tactile output (e.g., a“modifier-active tactile output”) corresponds to a different tactilesensation from the tactile sensation corresponding to a tactile output(e.g., a “no-modifier tactile output”) generated in response todetection of the decrease in intensity of contact 12006 below the secondactivation threshold without detection of a modifier input when theincrease in intensity of contact 12006 above the first activationthreshold is detected, as illustrated in FIGS. 8A-8C.

Thus, when an increase in the intensity of contact 12006 above the firstactivation threshold and a subsequent decrease in the intensity ofcontact 12006 below the second activation threshold are detected, theoperation that is performed depends on whether a modifier input isdetected while the increase in intensity above the first activationthreshold is detected. In some embodiments, the operation(s) performedin response to detection of the intensity decrease, after detection ofthe intensity increase without a modifier input, correspond tooperations associated with a left-click of a mouse (or similar inputdevice), and the operation(s) performed in response to detection of theintensity decrease, after detection of the intensity increase with amodifier input, correspond to operations associated with a right-clickof a mouse (or similar input device). Left-click operations include, forexample, activating an application launch or shortcut icon, displayingan application window corresponding to an application associated with anicon, selecting an icon or other user interface object, and so on.Right-click operations include, for example, displaying a context menu(e.g., context menu 12014 or 12024).

In some other embodiments, the association is, optionally, reversed; theoperation(s) performed in response to detection of the intensitydecrease, after detection of the intensity increase without a modifierinput, correspond to operations associated with a right-click of a mouse(or similar input device), and the operation(s) performed in response todetection of the intensity decrease, after detection of the intensityincrease with a modifier input, correspond to operations associated witha left-click of a mouse (or similar input device).

Further, the tactile output that is generated in response to thedetection of the decrease in the intensity of contact 12006, afterdetection of the increase in the intensity of contact 12006, depends onthe detection of, or lack of, a modifier input along with the detectionof the intensity increase. In some embodiments, the tactile outputgenerated when a modifier input is detected (e.g., a “modifier-activetactile output”) is different from the tactile output generated when nomodifier input is detected (e.g., a “no-modifier tactile output”) inamplitude, movement profile, or both.

In some embodiments, the operation that is performed, if any, inresponse to detection of the decrease in intensity of a contact afterdetection of the increase in intensity of the contact depends on theposition of the focus selector (e.g., cursor 12004) when the increase inintensity is detected, as well as whether a modifier input was detected.In the examples described above with reference to FIGS. 8A-8J, cursor12004 is positioned over user interface object 12002-2. FIG. 8K showscursor 12004 positioned over “empty space” on user interface 12000, awayfrom user interface objects 12002. Contact 12020 is detected ontouch-sensitive surface 451 at an intensity less than the firstactivation threshold (e.g., “IT_(L)”). In FIG. 8L, the device detects anincrease in intensity of contact 12020 above the first activationthreshold (e.g., “IT_(L)”). Then, the device detects a decrease inintensity of contact 12020 below the second activation threshold (e.g.,“IT₁”), as shown in FIG. 8M. In response to the decrease of theintensity below the second activation threshold, no operation isperformed. In some embodiments, left-clicks that occur when the focusselector is over empty space are ignored, and thus contact 12020 thatincreases and decreases in intensity with no modifier input while cursor12004 is over empty space does not cause the device to perform anoperation.

On the other hand, FIG. 8N shows a modifier input (e.g., contact 12022)detected concurrently with detection of an increase of the intensity ofcontact 12020 above the first activation threshold. Subsequently, thedevice detects a decrease in intensity of contact 12020 below the secondactivation threshold (e.g., “IT₁”), as shown in FIG. 8O. In response tothe decrease of the intensity below the second activation threshold,context menu 12024 is displayed on user interface 12000. Context menu12024 optionally includes different options than context menu 12014(FIG. 8E, 8G, or 8J), as the context is changed by the positioning ofcursor 12004 over empty space on user interface 12000 instead of userinterface object 12002-2. In some embodiments, right-clicks that occurwhen the focus selector is over empty space activate displaying of acontext menu, and thus contact 12020 that increases and decreases inintensity with a modifier input while cursor 12004 is over empty spacecause the device to display a context menu (e.g., context menu 12024).

As described above, different tactile outputs are, optionally, generateddepending on whether a modifier input was detected. FIGS. 8P-8Qillustrate example waveforms of movement profiles for generating thesetactile outputs. FIG. 8P illustrates dominant movement components of twodifferent tactile outputs with two different movement profiles (e.g., asawtooth waveform on the left and a square waveform on the right). Insome embodiments, one of the movement profiles (e.g., the sawtoothwaveform) corresponds to a tactile output (e.g., a “modifier-activetactile output”) for an increase and subsequent decrease in intensitydetected while a modifier input is detected; and the other movementprofile (e.g., the square waveform) corresponds to a tactile output(e.g., a “no-modifier tactile output”) for an increase and subsequentdecrease in intensity detected without detecting a modifier input. FIG.8Q illustrates dominant movement components of two different tactileoutputs with two different amplitudes (e.g., a high amplitude squarewaveform on the left and a low amplitude square waveform on the right).In some embodiments, one of the amplitudes (e.g., the high amplitudesquare waveform) corresponds to a tactile output (e.g., a“modifier-active tactile output”) for an increase and subsequentdecrease in intensity detected while a modifier input is detected; andthe other amplitude (e.g., the low amplitude square waveform)corresponds to a tactile output (e.g., a “no-modifier tactile output”)for an increase and subsequent decrease in intensity detected withoutdetecting a modifier input. In some embodiments both the amplitude andthe movement profile of the tactile output are selected in accordancewith a determination as to on whether or not the modifier input wasdetected when the device detected the increase prior to detecting thesubsequent decrease in intensity of the contact.

FIGS. 8R-8V illustrate an example of the user interfaces describedabove, with reference to FIGS. 8A-8Q, implemented on a device (e.g.,device 100) with a touch-sensitive display 112. FIG. 8R shows userinterface 12054 and user interface objects 12052 displayed in userinterface 12054, on touch-sensitive display 112 of a device. Userinterface objects 12052 are similar to user interface objects 12002described above; the details are not repeated here.

FIG. 8R also shows contact 12056 detected on user interface object12052-2. Contact 12056 as shown in FIG. 8R has an intensity that isbelow the first activation threshold (e.g., “IT_(L)”). An increase ofthe intensity of contact 12056 above the first activation threshold isdetected, as shown in FIG. 8S. After the detection of the increase, adecrease in the intensity of contact 12056 below the second activationthreshold (e.g., “IT₁”) is detected, as shown in FIG. 8T.

In response to the detection of the decrease in intensity of contact12056 below the second activation threshold, after detection of theincrease in the intensity of contact 12056 above the first activationthreshold, one or more operations associated with user interface object12052-2, over which contact 12056 is detected, are, optionally,performed. For example, if user interface object 12052-2 is an icon(e.g., an application launch or shortcut icon) corresponding to anapplication, window 12058 for the corresponding application is displayedin user interface 12054, as shown in FIG. 8T.

Additionally, in response to detection of the decrease in the intensityof contact 12056 below the second activation threshold, after detectionof the increase in the intensity of contact 12056 above the firstactivation threshold, a tactile output (e.g., a “no-modifier tactileoutput”) is generated on touch-sensitive display 112. The tactile outputis, optionally, generated in accordance with a movement profile (e.g.,movement profiles illustrated in FIGS. 8P-8Q).

Returning to FIG. 8R, the intensity of contact 12056 is, optionally,increased above the first activation threshold concurrently with thedetection of a modifier input. An example of a modifier input is anadditional contact that is detected on touch-sensitive display 112concurrently with detection of contact 12056. FIG. 8U shows contact12060 detected on touch-sensitive display 112 concurrently with thedetection of an increase in the intensity of contact 12056 above thefirst activation threshold (e.g., “IT_(L)”). Then, a decrease in theintensity of contact 12056 below the second activation threshold (e.g.,“IT₁”) is detected, as shown in FIG. 8V. In response to detection of thedecrease in the intensity of contact 12056 below the second activationthreshold, after concurrent detection of the increase in the intensityof contact 12056 above the first activation threshold and contact 12060,context menu 12062, which is similar to context menu 12014) is displayedin user interface 12054, as shown in FIG. 8V. In some embodiments,additional contact 12060 is determined to be a modifier input whencontact 12060 is detected in a predefined region (e.g., a region in thetop right, top left, bottom right, or bottom left corner) oftouch-sensitive display 112.

Additionally, in response to detecting the decrease in the intensity ofcontact 12056 below the second activation threshold, after concurrentdetection of the increase in the intensity of contact 12056 above thefirst activation threshold and a modifier input (e.g., contact 12060),the device generates a tactile output (e.g., a “modifier-active tactileoutput”) on touch-sensitive display 112. In some embodiments, thistactile output (e.g., a “modifier-active tactile output”) corresponds toa different tactile sensation from the tactile sensation correspondingto a tactile output (e.g., a “no-modifier tactile output”) generated inresponse to detection of the decrease in intensity of contact 12056below the second activation threshold without detection of a modifierinput when the increase in intensity of contact 12056 above the firstactivation threshold is detected.

FIGS. 9A-9B are flow diagrams illustrating a method 12100 of providingfeedback corresponding to modifier inputs in accordance with someembodiments. The method 12100 is performed at an electronic device(e.g., device 300, FIG. 3, or portable multifunction device 100, FIG.1A) with a display and a touch-sensitive surface. In some embodiments,the display is a touch screen display and the touch-sensitive surface ison the display. In some embodiments, the display is separate from thetouch-sensitive surface. Some operations in method 12100 are,optionally, combined and/or the order of some operations is, optionally,changed.

As described below, the method 12100 provides an intuitive way toperform operations based on modified inputs. The method reduces thecognitive burden on a user when providing feedback corresponding tomodifier inputs, thereby creating a more efficient human-machineinterface. For battery-operated electronic devices, enabling a user toperform operations based on modified inputs faster and more efficientlyconserves power and increases the time between battery charges.

The device detects (12102) a contact (e.g., a finger contact) on thetouch-sensitive surface. For example, contact 12006 (FIG. 8A or 8H) or12020 (FIG. 8K) is, optionally, detected on touch-sensitive surface 451.As another example, contact 12056 is, optionally, detected ontouch-sensitive display 112.

The device detects (12104) an increase in intensity of the contact abovea first activation threshold (e.g., “IT_(L)”). In some embodiments, thefirst activation threshold is an “increasing-intensity” activationthreshold that indicates a threshold at which a tactile output isgenerated when the intensity of the contact is increasing. The intensityof contact 12006, for example, is, optionally, increased from a levelbelow the first activation threshold (e.g., FIGS. 8A and 8H) to a levelabove the first activation threshold (e.g., FIG. 8B, 8D, 8F, or 8I), andthe increase is detected. Similarly, the intensity of contact 12020 is,optionally, increased from a level below the first activation thresholdto a level above the first activation threshold (FIGS. 8K-8L, 8N). Asanother example, the intensity of contact 12056 is, optionally,increased from a level below the first activation threshold to a levelabove the first activation threshold (FIGS. 8R-8S, 8U).

After detecting the increase in intensity of the contact above the firstactivation threshold, the device detects (12106) a reduction inintensity of the contact below a second activation threshold (e.g.,“IT₁”). In some embodiments, the second activation threshold is a“decreasing-intensity” activation threshold that indicates a thresholdat which a tactile output is generated when the intensity of the contactis decreasing. The intensity of contact 12006, for example, is,optionally, decreased to a level below the second activation threshold(e.g., FIG. 8C, 8E, 8G, or 8J), and the increase is detected. Similarly,the intensity of contact 12020 is, optionally, decreased to a levelbelow the second activation threshold (FIGS. 8M, and 8O). As anotherexample, the intensity of contact 12056 is, optionally, decreased to alevel below the second activation threshold (FIGS. 8T, and 8V).

In some embodiments, the second activation threshold is (12108)different from the first activation threshold (e.g., the firstactivation threshold is “IT_(L)” and the second activation threshold is“IT₁”). In some embodiments, the second activation threshold is (12110)the same as the first activation threshold (e.g., the first activationthreshold is “IT_(L)” and the second activation threshold is also“IT_(L)”).

In response to detecting the reduction in intensity of the contact belowthe second activation threshold (12112), in accordance with adetermination that a modifier input was detected while detecting theincrease in intensity of the contact above the first activationthreshold (12114), the device performs a first operation (12116) andgenerates (12118) a first tactile output on the touch-sensitive surface.For example, in FIG. 8D, modifier key 12010 is pressed when the increasein intensity of contact 12006 is detected. When the decrease in theintensity of contact 12006 is detected (FIG. 8E), context menu 12014 isdisplayed and a first tactile output (e.g., a “modifier-active tactileoutput”) is generated in response. Similar results occur with otherexamples of modifier inputs (for example, contact 12016, FIG. 8G;contact 12006 in area 12018, FIG. 8J; contact 12022, FIG. 8O). Asanother example, in FIG. 8U, additional contact 12060 is detected whenthe increase in intensity of contact 12056 is detected. When thedecrease in the intensity of contact 12056 is detected (FIG. 8V),context menu 12062 is displayed and a first tactile output (e.g., a“modifier-active tactile output”) is generated in response. In someembodiments, the combination of the intensity increase-decrease and themodifier input is associated with a right-click of a mouse or similarinput device; the combination activates operations associated with theright-click.

In some embodiments, the modifier input is (12120) an input selectedfrom the set consisting of: a key press of a modifier key, an additionalcontact on the touch-sensitive surface, and detecting the contact on apredefined portion of the touch-sensitive surface designated to modifyinputs (e.g., a predefined “right click” region on a touchpad or apredefined region of a touch-sensitive mouse that corresponds to a“right mouse button”). The modifier input is, optionally, for example,press 12012 of modifier key 12010 (FIG. 8D), additional contact 12016(FIG. 8F) or 12022 (FIG. 8N) or 12060 (FIG. 8U), or detection of contact12006 in area 12018 on touch-sensitive surface 451.

In response to detecting (12112) the reduction in intensity of thecontact below the second activation threshold (e.g., “IT₁”), inaccordance with a determination that the modifier input was not detected(12122) while detecting the increase in intensity of the contact abovethe first activation threshold (e.g., “IT_(L)”), the device performs(12124) second operation different from the first operation andgenerates (12126) a second tactile output (e.g., a “no-modifier tactileoutput”) on the touch-sensitive surface, where the second tactile outputis different from the first tactile output. For example, in FIG. 8B,there is no modifier input when the increase in intensity of contact12006 is detected, and thus when the decrease in the intensity ofcontact 12006 is detected (FIG. 8C), window 12008 is displayed and asecond tactile output (e.g., a “no-modifier tactile output”) isgenerated in response. As another example, in FIG. 8S, there is nomodifier input when the increase in intensity of contact 12056 isdetected, and thus when the decrease in the intensity of contact 12056is detected (FIG. 8T), window 12058 is displayed and a second tactileoutput (e.g., a “no-modifier tactile output”) is generated in response.In some embodiments, the combination of the intensity increase-decreaseand the lack of a modifier input is associated with a left-click of amouse or similar input device; the combination activates operationsassociated with the left-click.

In some embodiments, the first operation corresponds (12128) to aright-click operation (e.g., an operation corresponding to clicking onthe rightmost button of a two or three button mouse or trackpad,sometimes called a “right-click mouse operation”), and the secondoperation corresponds to a left-click operation (e.g., an operationcorresponding to clicking on the leftmost button of a two or threebutton mouse or trackpad, sometimes called a “left-click mouseoperation”). For example, the displaying of context menu 12014 or 12024or 12062 is a right-click operation, and the displaying of window 12008(FIG. 8C) is a left-click operation.

In some embodiments, the contact is detected on the touch-sensitivesurface while a focus selector is over an icon on the display, the firstoperation includes (12130) displaying a context menu that includesselectable options to perform operations associated with the icon, andthe second operation includes displaying a new application windowassociated with the icon (e.g., launching an application or, if theapplication has already been launched, opening a new window of theapplication that includes a document associated with the icon). Forexample, in FIGS. 8A-8J, contact 12006 is detected on touch-sensitivesurface 451 while cursor 12004 is displayed over user interface object12002-2. When there is no modifier input detected, window 12008 of anapplication associated with user interface object 12002-2 is displayed,as shown in FIG. 8C. When a modifier input is detected, context menu12014 is displayed, as shown in FIGS. 8E, 8G, and 8J. Context menu 12014includes selectable options to perform operations associated with userinterface object 12002-2. Analogously, in FIGS. 8R-8V, contact 12056 isdetected over user interface object 12052-2 on touch-sensitive display112. When there is no modifier input detected, window 12058 of anapplication associated with user interface object 12052-2 is displayed,as shown in FIG. 8T. When a modifier input is detected, context menu12062 is displayed, as shown in FIG. 8V. Context menu 12062 includesselectable options to perform operations associated with user interfaceobject 12052-2.

In some embodiments, the first tactile output is (12132) generated bymovement of the touch-sensitive surface that includes a first dominantmovement component (e.g., movement corresponding to the initial impulse,ignoring any unintended resonance), the second tactile output isgenerated by movement of the touch-sensitive surface that includes asecond dominant movement component, and the first dominant movementcomponent and the second dominant movement component have a samemovement profile (e.g., same waveform shape such as square, sine,squine, sawtooth, triangle, or approximately the same width/period) anddifferent amplitudes, as shown in FIG. 8Q. Thus, in some embodiments,the tactile outputs with and without the modifier input optionallydiffers in amplitude rather than in the movement profile, so that onetactile sensation is a stronger version of the other tactile sensation.In contrast, in some embodiments, the tactile output (e.g., a“modifier-active tactile output”) generated when a modifier input wasdetected and the tactile output (e.g., a “no-modifier tactile output”)generated when a modifier input was not detected both have respectivedominant movement components that have different respective movementprofiles (for example, the movement profiles depicted in FIG. 8P) witheither the same maximum amplitude or different maximum amplitudes.

It should be understood that the particular order in which theoperations in FIGS. 9A-9B have been described is merely exemplary and isnot intended to indicate that the described order is the only order inwhich the operations could be performed. One of ordinary skill in theart would recognize various ways to reorder the operations describedherein. Additionally, it should be noted that details of other processesdescribed herein with respect to other methods described herein (e.g.,those listed in the fifth paragraph of the Description of Embodiments)are also applicable in an analogous manner to method 12100 describedabove with respect to FIGS. 9A-9B. For example, the contacts, gestures,user interface objects, tactile outputs, intensity thresholds, and focusselectors described above with reference to method 12100 optionally hasone or more of the characteristics of the contacts, gestures, userinterface objects, tactile outputs, intensity thresholds, and focusselectors described herein with reference to other methods describedherein (e.g., those listed in the fifth paragraph of the Description ofEmbodiments). For brevity, these details are not repeated here.

In accordance with some embodiments, FIG. 10 shows a functional blockdiagram of an electronic device 12200 configured in accordance with theprinciples of the various described embodiments. The functional blocksof the device are, optionally, implemented by hardware, software, or acombination of hardware and software to carry out the principles of thevarious described embodiments. It is understood by persons of skill inthe art that the functional blocks described in FIG. 10 are, optionally,combined or separated into sub-blocks to implement the principles of thevarious described embodiments. Therefore, the description hereinoptionally supports any possible combination or separation or furtherdefinition of the functional blocks described herein.

As shown in FIG. 10, an electronic device 12200 includes a display unit12202, a touch-sensitive surface unit 12204 configured to receivecontacts, one or more sensor units 12205 configured to detect intensityof contacts with the touch-sensitive surface unit 12204, and aprocessing unit 12206 coupled to the display unit 12202, thetouch-sensitive surface unit 12204 and the sensor units 12205. In someembodiments, the processing unit 12206 includes a detecting unit 12208,a performing unit 12210, and a generating unit 12212.

The processing unit 12206 is configured to: detect a contact on thetouch-sensitive surface unit 12204 (e.g., with the detecting unit12208); detect an increase in intensity of the contact above a firstactivation threshold (e.g., with the detecting unit 12208); afterdetecting the increase in intensity of the contact above the firstactivation threshold, detect a reduction in intensity of the contactbelow a second activation threshold (e.g., with the detecting unit12208); and in response to detecting the reduction in intensity of thecontact below the second activation threshold: in accordance with adetermination that a modifier input was detected while detecting theincrease in intensity of the contact above the first activationthreshold: perform a first operation (e.g., with the performing unit12210) and generate a first tactile output on the touch-sensitivesurface unit 12204 (e.g., with the generating unit 12212); and inaccordance with a determination that the modifier input was not detectedwhile detecting the increase in intensity of the contact above the firstactivation threshold: perform a second operation different from thefirst operation (e.g., with the performing unit 12210) and generate asecond tactile output on the touch-sensitive surface unit 12204, whereinthe second tactile output is different from the first tactile output(e.g., with the generating unit 12212).

In some embodiments, the modifier input is an input selected from theset consisting of: a key press of a modifier key, an additional contacton the touch-sensitive surface unit 12204, and detection of the contacton a predefined portion of the touch-sensitive surface unit 12204designated to modify inputs.

In some embodiments, the first operation corresponds to a right-clickoperation, and the second operation corresponds to a left-clickoperation.

In some embodiments, the contact is detected on the touch-sensitivesurface unit 12204 while a focus selector is over an icon on the displayunit 12202, the first operation includes displaying a context menu thatincludes selectable options to perform operations associated with theicon, and the second operation includes displaying a new applicationwindow associated with the icon.

In some embodiments, the second activation threshold is different fromthe first activation threshold.

In some embodiments, the second activation threshold is the same as thefirst activation threshold.

In some embodiments, the first tactile output is generated by movementof the touch-sensitive surface unit 12204 that includes a first dominantmovement component, the second tactile output is generated by movementof the touch-sensitive surface unit 12204 that includes a seconddominant movement component, and the first dominant movement componentand the second dominant movement component have a same movement profileand different amplitudes.

The operations in the information processing methods described aboveare, optionally implemented by running one or more functional modules ininformation processing apparatus such as general purpose processors(e.g., as described above with respect to FIGS. 1A and 3) or applicationspecific chips.

The operations described above with reference to FIGS. 9A-9B are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.10. For example, detection operations 12102, 12104, and 12106,performing operations 12116 and 12124, and generating operations 12118and 12126 are, optionally, implemented by event sorter 170, eventrecognizer 180, and event handler 190. Event monitor 171 in event sorter170 detects a contact on touch-sensitive display 112, and eventdispatcher module 174 delivers the event information to application136-1. A respective event recognizer 180 of application 136-1 comparesthe event information to respective event definitions 186, anddetermines whether a first contact at a first location on thetouch-sensitive surface corresponds to a predefined event or sub-event,such as selection of an object on a user interface. When a respectivepredefined event or sub-event is detected, event recognizer 180activates an event handler 190 associated with the detection of theevent or sub-event. Event handler 190 optionally utilizes or calls dataupdater 176 or object updater 177 to update the application internalstate 192. In some embodiments, event handler 190 accesses a respectiveGUI updater 178 to update what is displayed by the application.Similarly, it would be clear to a person having ordinary skill in theart how other processes can be implemented based on the componentsdepicted in FIGS. 1A-1B.

Providing Feedback for Changing Activation States of a User Interface

Many electronic devices have graphical user interfaces that include userinterface objects, such as virtual buttons and switches. In somecircumstances, a user activates a user interface object to perform anoperation or adjust a parameter or property. To make a virtual button orswitch easier to use, the virtual object optionally mimics the behaviorof the corresponding physical object. For example, haptic sensationsare, in some circumstances, felt when a virtual switch is operated, withthe haptic sensations mimicking the sensations of the correspondingphysical switch, such as mimicking the clicks of a physical actuatormechanism (e.g., a mouse button) that activates the switch. But physicalobjects, such as real buttons and switches, will, in some circumstancesprovide excessive tactile feedback in some circumstances, and too littlefeedback in others. In such situations, a virtual object that justmimicked sensations of the corresponding physical object would alsoprovide too much (or too little) feedback. But a virtual object does nothave to be provided with haptic feedback that just mimics tactilesensations from the corresponding physical object. The embodimentsdescribed below provide tactile feedback that corresponds to changes inactivation states of a virtual button, switch or other user interfaceobject, rather than tactile feedback that corresponds 1:1 to tactilesensations that would be felt by a user when using a physical control toperform similar operations. When tactile sensations are provided foractivation state changes of the virtual button or switch, the user canbetter discern the activation state of the virtual button without beingdistracted or confused by too much or too little tactile feedback. Thisimproved haptic feedback for virtual objects enables the user to operatethe device more quickly and efficiently, thereby creating a moreefficient human-machine interface.

FIGS. 11A-11N illustrate exemplary user interfaces for providingfeedback for changing activation states of a user interface object inaccordance with some embodiments. The user interfaces in these figuresare used to illustrate the processes described below, including theprocesses in FIGS. 12A-12B. FIGS. 11A-11N include intensity diagramsthat show the current intensity of the contact on the touch-sensitivesurface relative to a plurality of intensity thresholds including alight press intensity threshold (e.g., “IT_(L)”) and a deep pressintensity threshold (e.g., “IT_(D)”). In some embodiments, operationssimilar to those described below with reference to “IT_(L)” and “IT_(D)”are performed with reference to different intensity thresholds.

FIG. 11A illustrates an example of a user interface that includes one ormore user interface objects. Image editor user interface 12300 isdisplayed on display 450 (e.g., display 340) of a device (e.g., device300). Image 12302 is displayed in image editor user interface 12300 forediting in accordance with user commands. One or more user interfaceobjects (for example, buttons, sliders, rocker switches) optionallyinclude control user interface objects such as rocker switches 12304 andstatus user interface objects such as value indicators 12306 displayedin image editor user interface 12300. The user interface objects in FIG.11A-11G are configured to enable a user to issue commands for editingimage 12302 and the user interface objects in FIG. 11H-11N areconfigured to enable a user to issue commands for editing image 12322.For example, one or more rocker switches 12304, for modifying respectiveparameters of image 12302, are displayed in image editor user interface12300. Values representing respective parameters are, optionally,displayed in respective value indicators 12306. Rocker switch 12304-1enables a user to modify the brightness of image 12302, for example, andthe brightness value (for example, represented by integers, with 0 asthe middle value between the upper and lower bounds) is displayed invalue indicator 12306-1. Clearly, a middle value of 0 is merelyexemplary. For example, an upper bound of 100 and a lower bound of 0would have a middle value of 50 (not shown), etc. Cursor 12308 is alsodisplayed in user interface 12300. In some embodiments, cursor 12308 isa mouse pointer. Cursor 12308 is an example of a focus selector.

A respective rocker switch 12304 optionally has a “minus” portion forreducing the value of a parameter associated with the rocker switch,indicated by the minus sign, and a “plus” portion for increasing thevalue of a parameter associated with the rocker switch, indicated by aplus sign. A rocker switch 12304 is, optionally, activated when a focusselector (e.g., cursor 12308) is positioned over a portion of the rockerswitch and an intensity of a contact associated with the focus selectorchanges. In some embodiments, the corresponding value decreases orincreases depending on the portion over which the focus selector ispositioned. When the focus selector is positioned over the “minus”portion, the corresponding value decreases when the rocker switch isactivated. When the focus selector is positioned over the “plus”portion, the corresponding value increases when the rocker switch isactivated. In FIG. 11A, cursor 12308 is positioned over the “minus”portion of rocker switch 12304-1.

While rocker switch 12304-1 is not activated, rocker switch 12304-1 isdisplayed in a neutral position, as shown FIG. 11A. When rocker switch12304-1 is activated, rocker switch 12304-1 is displayed as if eitherthe “minus” portion (if cursor 12308 is positioned over the “minus”portion when rocker switch 12304-1 is activated, thus rocker switch12304-1 is activated to decrease the value) or the “plus” portion (ifcursor 12308 is positioned over the “plus” portion when rocker switch12304-1 is activated, thus rocker switch 12304-1 is activated toincrease the value) is depressed, as shown in FIG. 11B (for the “minus”portion being depressed) and FIG. 11E (for the “plus” portion beingdepressed), respectively. In some embodiments, when rocker switch12304-1 is activated, an animation showing a transition of rocker switch12304-1 from the neutral position to either depressed position isdisplayed; and when rocker switch 12304-1 is deactivated, an animationshowing a transition of rocker switch 12304-1 from either depressedposition to the neutral position is displayed.

FIG. 11A shows contact 12310 detected on touch-sensitive surface 451(e.g., touchpad 355) of the device at an intensity that is above acontact detection threshold (e.g., “IT₀”) and below a light pressintensity threshold (e.g., “IT_(L)”) for activating rocker switch12304-1. While contact 12310 continues to be detected on touch-sensitivesurface 451 and cursor 12308 is positioned over the “minus” portion ofrocker switch 12304-1, the intensity of contact 12310 is, in somecircumstances, increased to a first intensity that is above the lightpress intensity threshold (e.g., “IT_(L)”) for activating rocker switch12304-1, and the increase in intensity is detected, as shown in FIG.11B. In response to the detection of the increase in intensity, rockerswitch 12304-1 is activated and the brightness value in value indicator12306-1 decreases. The brightness of image 12302 changes in accordancewith the change in the brightness value. In some embodiments, thebrightness value decreases at a relatively slow rate (e.g., −1 in valueper second). In some embodiments, rocker switch 12304-1 is animated toshow the “minus” portion being depressed. In some embodiments, thebrightness value continues to decrease as long as the intensity ofcontact 12310 does not decrease below the light press intensitythreshold (e.g., “IT_(L)”).

The intensity of contact 12310 is, in some circumstances, increasedfurther. While contact 12310 continues to be detected on touch-sensitivesurface 451 and cursor 12308 is still positioned over the “minus”portion of rocker switch 12304-1, the device detects an increase inintensity of contact 12310 from the first intensity (e.g., an intensitybetween IT_(L) and IT_(D)) to a second, higher intensity that is above adeep press intensity threshold (e.g., “IT_(D)”). In response to thisincrease in intensity, rocker switch 12304-1 changes to a furtheractivation state, as shown in FIG. 11C where the portion of the rockerswitch under focus selector 12308 is pushed “into” the display, and thebrightness value of image 12302 decreases at a rate that is faster(e.g., −10 per second) than the rate of decrease at the first intensity,and the brightness of image 12302 changes in accordance with the changein the brightness value, as shown in FIG. 11C.

The intensity of contact 12310 is, in some circumstances, then decreasedbelow the light press intensity threshold (e.g., “IT_(L)”) quickly(e.g., from the second intensity above IT_(D) to an intensity belowIT_(L) in 0.05 seconds or less). In response to the detection of thedecrease in intensity below the light press intensity threshold (e.g.,“IT_(L)”), the brightness value stops changing, and the brightness ofimage 12302 stops changing, as shown in FIG. 11D. Depending on the rateat which the intensity decreased from the second intensity to anintensity below the light press intensity threshold (e.g., “IT_(L)”),the brightness value optionally stops changing immediately in responseto the detection of the intensity decrease, or the rate of change in thebrightness value optionally first decreases to a slower rate (e.g., therate at the first intensity) before the brightness values stopschanging.

Rocker switch 12304-1 includes multiple activation states. In someembodiments, the activation states for rocker switch 12304-1 aredifferent brightness levels as the brightness value changes. In someembodiments, when the brightness value is decreasing at the “slow” rate(e.g., −1 per second), each brightness value increment based on the rateof decrease (e.g., −1, −2, −3, so forth) is considered to be anactivation state, and when the brightness value is decreasing at the“fast” rate (e.g., −10 per second), each brightness value incrementbased on the rate of decrease (e.g., each −10th increment) is consideredto be an activation state. In some of these embodiments, at eachactivation state, a tactile output is, optionally, generated ontouch-sensitive surface 451. For example, when the value decreases from−1 to −2, then to −3 and then to −13, tactile outputs are, optionally,generated at −2, −3, and −13.

In some other embodiments, the activation states are the different ratesat which the brightness value changes. For example, the “slow” rate isone activation state, the “fast” rate is another activation state, andcessation of activation of rocker switch 12304-1 (e.g., a rate of 0 persecond) is another activation state of the rocker switch. A tactileoutput is, optionally, generated whenever the rate of decrease orincrease for the brightness value changes or when rocker switch 12304-1is activated or ceases to be activated. For example, when the brightnessvalue is not changing, rocker switch 12304-1 is in a first (“neutral”)activation state; when the brightness value is decreasing at the “slow”rate (e.g., −1 per second), rocker switch 12304-1 is in a second (“lightpress”) activation state; and when the brightness value is decreasing atthe “fast” rate (e.g., −10 per second), rocker switch 12304-1 is in athird (“deep press”) activation state. At each activation state, atactile output is, optionally, generated on touch-sensitive surface 451.For example, when the activation state changes from the first(“neutral”) activation state shown in FIG. 11A to the second (“lightpress”) activation state shown in FIG. 11B, the device generates atactile output corresponding to the change in activation state. Asanother example, when the activation state changes from the second(“light press”) activation state shown in FIG. 11B to the third (“deeppress”) activation state shown in FIG. 11C, the device generates atactile output corresponding to the change in activation state.

In some embodiments, the tactile output generated in response to achange in activation state optionally varies depending on whether thechange in activation state was in response to an increase or a decreasein the intensity of contact 12310. A tactile output generated for anactivation state change in response to an increase in intensity is,optionally, different from a tactile output generated for an activationstate change in response to a decrease in intensity. The tactile outputsare, optionally, different in movement profile, amplitude, or both. Insome embodiments, a tactile output generated for an activation statechange in response to an increase in intensity corresponds to a tactilesensation that simulates a down-click (e.g., press-and-hold) of aphysical button (e.g., a mouse button), and a tactile output generatedfor an activation state change in response to a decrease in intensitycorresponds to a tactile sensation that simulates an up-click (e.g.,release from a press-and-hold) of a physical button.

Returning to FIG. 11D, cursor 12308 has been moved (e.g., from location12308-a to location 12308-b) to the “plus” portion of rocker switch12304-1 (e.g., in accordance with movement of contact 12310 acrosstouch-sensitive surface 451 while contact 12310 has an intensity betweenIT₀ and IT_(L) from location 12310-a to location 12310-b in FIG. 11D).The intensity of contact 12310 is increased to the second intensityquickly (e.g., the intensity of contact 12310-b increases from anintensity below the IT_(L) in FIG. 11D to the second intensity that isabove IT_(D) in FIG. 11E in 0.05 seconds or less), as shown in FIG. 11E.In response to the increase in intensity, the brightness value increasesat the “fast” rate (e.g., +10 per second). As shown in FIG. 11D, rockerswitch 12304-1 is in the neutral activation state and transitionsdirectly to the deep press activation state in FIG. 11E in response to arapid increase in intensity of contact 12310 to an intensity aboveIT_(D).

As shown in FIG. 11F, the intensity of contact 12310 is subsequentlydecreased from the second intensity (e.g., an intensity above IT_(D)) tothe first intensity (e.g., an intensity between IT_(L) and IT_(D)). Inresponse to detecting the intensity decrease to the first intensity, thebrightness value increases at the “slow” rate (e.g., +1 per second), asshown in FIG. 11F and rocker switch 12304-1 is shown in the light pressactivation state.

As shown in FIG. 11G, the intensity of contact 12310 is subsequentlydecreased further, from the first intensity (e.g., an intensity betweenIT_(L) and IT_(D)) to an intensity below the light press intensitythreshold (e.g., “IT_(L)”). In response to the further decrease inintensity of contact 12310, the brightness value stops increasing (e.g.,the rate of change becomes 0 per second), as shown in FIG. 11G androcker switch 12304-1 is shown in the neutral activation state.

As described above, the activation states of rocker switch 12304-1optionally correspond to the increments of change in the value, inaccordance with the rate of change, or the different rates of change. Atactile output is, optionally, generated whenever one activation statechanges to another (e.g., one increment to the next or one rate ofchange to the next).

FIGS. 11H-11N illustrate an example of the user interfaces describedabove, with reference to FIGS. 11A-11G, implemented on a device (e.g.,device 100) with a touch-sensitive display 112. FIG. 11H illustratesimage editor user interface 12328 displayed on touch-sensitive display112 of a device. Image 12322 is displayed in image editor user interface12328 for editing in accordance with user commands. One or more userinterface objects (for example, buttons, sliders, rocker switches)optionally include control user interface objects such as rockerswitches 12324 and status user interface objects such as valueindicators 12326 displayed in image editor user interface 12328. Theuser interface objects in FIGS. 11H-11N are configured to enable a userto issue commands for editing image 12322. For example, one or morerocker switches 12324, for modifying respective parameters of image12322, are displayed in image editor user interface 12328. Valuesrepresenting respective parameters are, optionally, displayed inrespective value indicators 12326. Rocker switch 12324-1 enables a userto modify the brightness of image 12322 in accordance with changes inintensity of contact 12330 while a focus selector is over rocker switch12324-1, for example, and the brightness value (for example, representedby integers, with 0 as the middle value between the upper and lowerbounds) is displayed in value indicator 12326-1. Contact 12330 is anexample of a focus selector.

A respective rocker switch 12324 optionally has a “minus” portion forreducing the value of a parameter associated with the rocker switch,indicated by the minus sign, and a “plus” portion for increasing thevalue of a parameter associated with the rocker switch, indicated by aplus sign. A rocker switch 12324 is, optionally activated when a contactis positioned over a portion of the rocker switch and an intensity of acontact associated with the focus selector changes. In some embodiments,the corresponding value decreases or increases depending on the portionover which the contact is positioned. When the contact is positionedover the “minus” portion, the corresponding value decreases when therocker switch is activated. When the contact is positioned over the“plus” portion, the corresponding value increases when the rocker switchis activated. In FIG. 11H, contact 12330 is positioned over the “minus”portion of rocker switch 12324-1.

While rocker switch 12324-1 is not activated, rocker switch 12324-1 isdisplayed in a neutral position, as shown FIG. 11H. When rocker switch12324-1 is activated, rocker switch 12324-1 is displayed as if eitherthe “minus” portion (if contact 12330 is positioned over the “minus”portion when rocker switch 12324-1 is activated, thus rocker switch12324-1 is activated to decrease the value) or the “plus” portion (ifcontact 12330 is positioned over the “plus” portion when rocker switch12324-1 is activated, thus rocker switch 12324-1 is activated toincrease the value) is depressed, as shown in FIG. 11I (for the “minus”portion being depressed) and FIG. 11L (for the “plus” portion beingdepressed), respectively. In some embodiments, when rocker switch12324-1 is activated, an animation showing a transition of rocker switch12324-1 from the neutral position to either depressed position isdisplayed; and when rocker switch 12324-1 is deactivated, an animationshowing a transition of rocker switch 12324-1 from either depressedposition to the neutral position is displayed.

FIG. 11H shows contact 12330 detected on touch-sensitive display 112 atan intensity that is above a contact detection threshold (e.g., “IT₀”)and below a light press intensity threshold (e.g., “IT_(L)”) foractivating rocker switch 12324-1. While contact 12330 continues to bedetected on touch-sensitive display 112 over the “minus” portion ofrocker switch 12324-1, the intensity of contact 12330 is, in somecircumstances, increased to a first intensity that is above the lightpress intensity threshold (e.g., “IT_(L)”) for activating rocker switch12324-1, and the increase in intensity is detected, as shown in FIG.11I. In response to the detection of the increase in intensity, rockerswitch 12324-1 is activated and the brightness value in value indicator12326-1 decreases. The brightness of image 12322 changes in accordancewith the change in the brightness value. In some embodiments, thebrightness value decreases at a relatively slow rate (e.g., −1 in valueper second). In some embodiments, rocker switch 12324-1 is animated toshow the “minus” portion being depressed. In some embodiments, thebrightness value continues to decrease as long as the intensity ofcontact 12330 does not decrease below the light press intensitythreshold (e.g., “IT_(L)”).

The intensity of contact 12330 is, in some circumstances, increasedfurther. While contact 12330 continues to be detected on touch-sensitivedisplay 112 over the “minus” portion of rocker switch 12324-1, thedevice detects an increase in intensity of contact 12330 from the firstintensity (e.g., an intensity between IT_(L) and IT_(D)) to a second,higher intensity that is above a deep press intensity threshold (e.g.,“IT_(D)”). In response to this increase in intensity, rocker switch12324-1 changes to a further activation state, as shown in FIG. 11Jwhere the portion of the rocker switch under contact 12330 is pushed“into” the display, and the brightness value of image 12322 decreases ata rate that is faster (e.g., −10 per second) than the rate of decreaseat the first intensity, and the brightness of image 12322 changes inaccordance with the change in the brightness value, as shown in FIG.11J.

The intensity of contact 12330 is, in some circumstances, then decreasedbelow the light press intensity threshold (e.g., “IT_(L)”) quickly(e.g., from the second intensity above IT_(D) to an intensity belowIT_(L) in 0.05 seconds or less). In response to the detection of thedecrease in intensity below the light press intensity threshold (e.g.,“IT_(L)”), the brightness value stops changing, and the brightness ofimage 12322 stops changing, as shown in FIG. 11K. Depending on the rateat which the intensity decreased from the second intensity to anintensity below the light press intensity threshold (e.g., “IT_(L)”),the brightness value optionally stops changing immediately in responseto the detection of the intensity decrease, or the rate of change in thebrightness value optionally first decreases to a slower rate (e.g., therate at the first intensity) before the brightness values stopschanging.

Rocker switch 12324-1 includes multiple activation states. In someembodiments, the activation states for rocker switch 12324-1 aredifferent brightness levels as the brightness value changes. In someembodiments, when the brightness value is decreasing at the “slow” rate(e.g., −1 per second), each brightness value increment based on the rateof decrease (e.g., −1, −2, −3, so forth) is considered to be anactivation state, and when the brightness value is decreasing at the“fast” rate (e.g., −10 per second), each brightness value incrementbased on the rate of decrease (e.g., each −10th increment) is consideredto be an activation state. In some of these embodiments, at eachactivation state, a tactile output is, optionally, generated ontouch-sensitive display 112. For example, when the value decreases from−1 to −2, then to −3 and then to −13, tactile outputs are, optionally,generated at −2, −3, and −13.

In some other embodiments, the activation states are the different ratesat which the brightness value changes. For example, the “slow” rate isone activation state, the “fast” rate is another activation state, andcessation of activation of rocker switch 12324-1 (e.g., a rate of 0 persecond) is another activation state. A tactile output is, optionally,generated whenever the rate of decrease or increase for the brightnessvalue changes or when rocker switch 12324-1 is activated or ceases to beactivated. For example, when the brightness value is not changing,rocker switch 12324-1 is in a first (“neutral”) activation state; whenthe brightness value is decreasing at the “slow” rate (e.g., −1 persecond), rocker switch 12324-1 is in a second (“light press”) activationstate; and when the brightness value is decreasing at the “fast” rate(e.g., −10 per second), rocker switch 12324-1 is in a third (“deeppress”) activation state. At each activation state, a tactile output is,optionally, generated on touch-sensitive display 112. For example, whenthe activation state changes from the first (“neutral”) activation stateshown in FIG. 11H to the second (“light press”) activation state shownin FIG. 11I, the device generates a tactile output corresponding to thechange in activation state. As another example, when the activationstate changes from the second (“light press”) activation state shown inFIG. 11I to the third (“deep press”) activation state shown in FIG. 11J,the device generates a tactile output corresponding to the change inactivation state.

In some embodiments, the tactile output generated in response to achange in activation state optionally varies depending on whether thechange in activation state was in response to an increase or a decreasein the intensity of contact 12330. A tactile output generated for anactivation state change in response to an increase in intensity is,optionally, different from a tactile output generated for an activationstate change in response to a decrease in intensity. The tactile outputsis, optionally, different in movement profile, amplitude, or both. Insome embodiments, a tactile output generated for an activation statechange in response to an increase in intensity corresponds to a tactilesensation that simulates a down-click (e.g., press-and-hold) of aphysical button (e.g., a mouse button), and a tactile output generatedfor an activation state change in response to a decrease in intensitycorresponds to a tactile sensation that simulates an up-click (e.g.,release from a press-and-hold) of a physical button.

Returning to FIG. 11K, contact 12330 has been moved (e.g., from location12330-a to location 12330-b while contact 12330 has an intensity betweenIT₀ and IT_(L)) to the “plus” portion of rocker switch 12324-1. Theintensity of contact 12330 is increased to the second intensity quickly(e.g., the intensity of contact 12330 increases from an intensity belowIT_(L) of contact 12330-b in FIG. 11K to the second intensity that isabove IT_(D) in FIG. 11L in 0.05 seconds or less), as shown in FIG. 11L.In response to the increase in intensity, the brightness value increasesat the “fast” rate (e.g., +10 per second). As shown in FIG. 11K, rockerswitch 12324-1 is in the neutral activation state and transitionsdirectly to the deep press activation state in FIG. 11L in response to arapid increase in intensity of contact 12330 to an intensity aboveIT_(D).

As shown in FIG. 11M, the intensity of contact 12330 is subsequentlydecreased from the second intensity (e.g., an intensity above IT_(D)) tothe first intensity (e.g., an intensity between IT_(L) and IT_(D)). Inresponse to detecting the intensity decrease to the first intensity, thebrightness value increases at the “slow” rate (e.g., +1 per second), asshown in FIG. 11M and rocker switch 12324-1 is shown in the light pressactivation state.

As shown in FIG. 11N, the intensity of contact 12330 is subsequentlydecreased further, from the first intensity (e.g., an intensity betweenIT_(L) and IT_(D)) to an intensity below the light press intensitythreshold (e.g., “IT_(L)”). In response to the further decrease inintensity of contact 12330, the brightness value stops increasing (e.g.,the rate of change becomes 0 per second), as shown in FIG. 11N, androcker switch 12324-1 is shown in the neutral activation state.

As described above, the activation states of rocker switch 12324-1optionally correspond to the increments of change in the value, inaccordance with the rate of change, or the different rates of change. Atactile output is, optionally, generated whenever one activation statechanges to another (e.g., one increment to the next or one rate ofchange to the next).

FIGS. 12A-12B are flow diagrams illustrating a method 12400 of providingfeedback for changing activation states of a user interface object inaccordance with some embodiments. The method 12400 is performed at anelectronic device (e.g., device 300, FIG. 3, or portable multifunctiondevice 100, FIG. 1A) with a display and a touch-sensitive surface. Insome embodiments, the display is a touch screen display and thetouch-sensitive surface is on the display. In some embodiments, thedisplay is separate from the touch-sensitive surface. Some operations inmethod 12400 are, optionally, combined and/or the order of someoperations is, optionally, changed.

As described below, the method 12400 provides a more efficient way toprovide feedback when changing activation states of a user interfaceobject. The method reduces the cognitive burden on a user when changingactivation states of a user interface object, thereby creating a moreefficient human-machine interface. For battery-operated electronicdevices, enabling a user to change activation states of a user interfaceobject faster and more efficiently conserves power and increases thetime between battery charges.

The device displays (12402) a user interface object on the display,where the user interface object has a plurality of activation states.FIG. 11A, for example, shows rocker switches 12304, for adjustingparameters of an image, displayed in image editor user interface 12300on a display 450 that is separate from a touch-sensitive surface 451 onwhich contacts are detected. As another example, FIG. 11H shows rockerswitches 12324, for adjusting parameters of an image, displayed in imageeditor user interface 12328 on a touch-sensitive display 112 on whichcontacts are detected. A respective rocker switch 12304 or 12324 hasmultiple activation states, which are, optionally, the increments ofchange in the corresponding parameter value or the rates of change inthe parameter value (e.g., a neutral activation state, a light pressactivation state and a deep press activation state).

The device detects (12404) a contact (e.g., a finger contact) on thetouch-sensitive surface. As shown in FIG. 11A, for example, contact12310 is detected on touch-sensitive surface 451. As another example,FIG. 11H shows contact 12330 detected on touch-sensitive display 112.

The device detects (12406) an increase of intensity of the contact onthe touch-sensitive surface from a first intensity (e.g., an intensitybetween IT_(L) and IT_(D)) to a second intensity (e.g., an intensityabove IT_(D)). FIGS. 11A-11C shows an increase in the intensity ofcontact 12310 from an intensity below a light press intensity threshold(e.g., “IT_(L)”) for activating rocker switch 12304-1, to a firstintensity that is higher than the light press intensity threshold (e.g.,“IT_(L)”), and then to a second intensity that is higher than the firstintensity. As another example, in FIGS. 11D-11E, the device detects anincrease in the intensity of contact 12310, from an intensity below thelight press intensity threshold (e.g., “IT_(L)”), quickly (e.g.,intensity increases from the below-threshold intensity to the secondintensity in 0.05 seconds or less) to a second intensity that is higherthan the first intensity. In FIGS. 11H-11J, the device detects anincrease in the intensity of contact 12330 from an intensity below alight press intensity threshold (e.g., “IT_(L)”) for activating rockerswitch 12324-1, to a first intensity that is higher than the light pressintensity threshold (e.g., “IT_(L)”), and then to a second intensitythat is higher than the first intensity. As another example, in FIGS.11K-11L, the device detects an increase in the intensity of contact12330, from an intensity below the light press intensity threshold(e.g., “IT_(L)”), quickly (e.g., intensity increases from thebelow-threshold intensity to the second intensity in 0.05 seconds orless) to a second intensity that is higher than the first intensity.

In response to detecting the increase in intensity (12408), the devicechanges (12410) activation states of the user interface object M times,where M is a positive integer, and generates (12412) a tactile output onthe touch-sensitive surface corresponding to each change in activationstate of the user interface object. For example, in FIG. 11A-11C or11H-11J, in response to the detection of the increase in intensity frombelow the light press intensity threshold (e.g., “IT_(L)”) to the firstintensity (e.g., an intensity between IT_(L) and IT_(D)) and then to thesecond intensity (e.g., an intensity above IT_(D)), the rocker switchchanges from a neutral activation state (corresponding to no change inbrightness of the image) to a light press activation state(corresponding to a slow rate of change in brightness of the image) andthen to a deep press activation state (corresponding to a fast rate ofchange in brightness of the image). Here, the activation state (in thiscase, the rate of change) changes two times, and two tactile outputs aregenerated.

As another example, in FIG. 11D-11E or 11K-11L, in response to thedetection of the rapid increase in intensity from below the light pressintensity threshold (e.g., “IT_(L)”) to the second intensity (e.g., anintensity above IT_(D)), the rocker switch changes from the neutralactivation state (corresponding to no change in brightness of the image)to the deep press activation state (corresponding to a fast rate ofchange in brightness of the image), skipping the light press activationstate (corresponding to a slow rate of change in brightness of theimage). Here, the activation state (in this case, the rate of change)changes once, and one tactile output is generated, even though thedevice has detected a change in intensity of the contact that has thesame magnitude as the change in intensity of contact 12310 between FIGS.11A and 11C.

In some embodiments, the user interface object has a first appearance ina first activation state; the user interface object has a secondappearance, different from the first appearance, in a second activationstate; and in response to detecting the increase in intensity, thedevice displays (12414) an animation of the user interface objecttransitioning from the first appearance to the second appearance. Rockerswitch 12304-1 appears in a plurality of activation states in FIGS.11A-11G, for example, rocker switch 12304-1 appears in a neutralposition when the rate of change is 0 (e.g., rocker switch 12304-1 is ina neutral activation state as shown in FIGS. 11A, 11D and 11G) andappears with either the “minus” portion or the “plus” portion depressedwhen the rate is non-zero (e.g., rocker switch 12304-1 is in a lightpress activation state as shown in FIGS. 11B and 11F or in a deep pressactivation state as shown in FIGS. 11C and 11E). When rocker switch12304-1 is activated or deactivated (e.g., the rate of change changes),an animation showing a transition from the neutral position to adepressed position, or vice versa, respectively, is, optionally,displayed. Rocker switch 12324-1 appears in a plurality of activationstates in FIGS. 11H-11N, for example, rocker switch 12324-1 appears in aneutral position when the rate of change is 0 (e.g., rocker switch12324-1 is in a neutral activation state as shown in FIGS. 11H, 11K and11N) and appears with either the “minus” portion or the “plus” portiondepressed when the rate is non-zero (e.g., rocker switch 12324-1 is in alight press activation state as shown in FIGS. 11I and 11M or in a deeppress activation state as shown in FIGS. 11J and 11L). When rockerswitch 12324-1 is activated or deactivated (e.g., the rate of changechanges), an animation showing a transition from the neutral position toa depressed position, or vice versa, respectively, is, optionally,displayed.

The device detects (12416) a decrease of intensity of the contact fromthe second intensity to the first intensity. As shown in FIGS. 11C-11D,for example, a quick decrease in the intensity of contact 12310 from thesecond intensity to below the light press intensity threshold (e.g.,“IT_(L)”) is detected. As another example, in FIGS. 11E-11G, a decreasein the intensity of contact 12310 from the second intensity to the firstintensity and then to below the light press intensity threshold (e.g.,“IT_(L)”) is detected. As further examples, in FIGS. 11J-11K, forexample, a quick decrease in the intensity of contact 12330 from thesecond intensity to below the light press intensity threshold (e.g.,“IT_(L)”) is detected. In FIGS. 11L-11N, a decrease in the intensity ofcontact 12330 from the second intensity to the first intensity and thento below the light press intensity threshold (e.g., “IT_(L)”) isdetected.

In response to the detection of the decrease in intensity (12418), thedevice changes (12420) activation states of the user interface object Ntimes, where N is a positive integer, and generates (12424) a tactileoutput on the touch-sensitive surface corresponding to each change inactivation state of the user interface object, where N is different fromM. For example, in FIGS. 11C-11D or FIGS. 11J-11K, in response to thedetection of the decrease in intensity, the rate of change in thebrightness value changes from the “fast” rate (e.g., the deep pressactivation state of rocker switch 12324-1) to 0 (e.g., the neutralactivation state of rocker switch 12324-1), and one tactile output isgenerated, whereas two tactile outputs were generated in response todetecting the increase in intensity in FIGS. 11A-11C and 11H-11J,respectively. As another example, in FIG. 11E-11G or 11L-11N, inresponse to the detection of the decrease in intensity, the rate ofchange in the brightness value changes from 0 (e.g., the neutralactivation state of rocker switch 12324-1) to the “slow” rate (e.g., thelight press activation state of rocker switch 12324-1) and then the“fast” rate (e.g., the deep press activation state of rocker switch12324-1), and two tactile outputs are generated, whereas just onetactile output was generated in response to detecting the increase inintensity in FIGS. 11D-11E and 11K-11L, respectively.

In some embodiments, a distinct tactile output is a tactile output thatwas generated to provide feedback corresponding to a user interfaceevent (e.g., a change in the activation state of the user interfaceobject, such as activation of a button or other control). In someembodiments, the touch-sensitive surface is moved by an actuator inaccordance with a separate waveform for each user interface event. Thewaveforms for different user interface events optionally overlap, but awaveform that was generated to provide a tactile feedback for aparticular user interface event (e.g., activation of a button or changein activation state of a control such as a rocker switch) will stillgenerate a distinct tactile output. In some embodiments, an activationstate of a user interface object corresponds to an operational state ofan application on the electronic device, and changing activation statesof the user interface object changes operational states of theapplication. If the user interface object is an adjustable controlinterface such as a multi-state button, rocker-switch or slider, theactivation states of the button/switch/slider are typically displayed bychanging the visual appearance of the adjustable control interface(e.g., as a change in shading of a button, a change in rotation of arocker switch or a change in position of a slider). Additionally, whenthe activation state of the button/switch/slider is changed, operationof an application associated with the button/switch/slider is changedaccordingly. For example, if a rocker switch controls the brightness ofan image, the activation states of the rocker switch correspond todifferent brightness levels of the image, and when the rocker switchchanges from a first activation state to a second activation state, thebrightness of the image changes from a first brightness levelcorresponding to the first activation state of the rocker switch to asecond brightness level corresponding to the second activation state ofthe rocker switch. In some embodiments, activation states correspond toimage property levels (e.g., hue, saturation, exposure, brightness,contrast), content navigation states (e.g., channel selection, forwardnavigation, backward navigation, frame-by-frame navigation), systemproperty adjustments (e.g., volume control, screen brightness, date/timesettings), rates of change (e.g., the rate at which an adjustableparameter value increases or decreases, speed of forward or backwardseeking through video or audio), or other adjustable properties.

In some embodiments, M is (12424) greater than N. In FIG. 11A-11D or11H-11K, for example, the number of changes in activation state inresponse to the detection of the increase in intensity of the contact(e.g., a change from the neutral activation state to the light pressactivation state and a change from the light press activation state tothe deep press activation state shown in FIGS. 11A-11C and 11H-11J) isgreater than the number of changes in activation state in response tothe detection of the decrease in intensity of the contact (e.g., achange from the deep press activation state to the neutral activationstate shown in FIGS. 11C-11D and FIGS. 11J-11K).

In some embodiments, M is (12426) less than N. In FIG. 11D-11G or11K-11N, for example, the number of changes in activation state inresponse to the detection of the increase in intensity of the contact(e.g., a change from the neutral activation state to the deep pressactivation state shown in FIGS. 11D-11E and 11K-11L) is less than thenumber of changes in activation state in response to the detection ofthe decrease in intensity of the contact (e.g., a change from the deeppress activation state to the light press activation state and a changefrom the light press activation state to the neutral activation stateshown in FIGS. 11E-11G and 11L-11N).

In some embodiments, M is (12428) equal to 1 and N is equal to 2. InFIG. 11D-11G or 11K-11N, for example, there is one change in activationstate in response to the detection of the increase in intensity and twochanges in activation state in response to the detection of the decreasein intensity.

In some embodiments, M is equal to 2 and N is (12430) equal to 1. InFIG. 11A-11D or 11H-11K, for example, there are two changes inactivation state in response to the detection of the increase inintensity and one change in activation state in response to thedetection of the decrease in intensity.

In some embodiments, at least one tactile output generated in responseto detecting the increase in intensity corresponds (12432) to a tactilesensation that simulates a down-click of a physical actuator mechanism(e.g., a simulation of the physical “down-click sensation” generated bythe mechanical button apparatus of a physical button when a useractivates the physical button), and at least one tactile outputgenerated in response to detecting the decrease in intensity correspondsto a tactile sensation that simulates an up-click of a physical actuatormechanism (e.g., a simulation of the physical “up-click sensation”generated by the mechanical button apparatus of a physical button when auser activates the physical button). For example, the tactile outputsgenerated for the activation state changes in response to the detectionof the increase in intensity of contact 12310 or 12330 correspond totactile sensations that simulate a down-click, and the tactile outputsgenerated for the activation state changes in response to the detectionof the decrease in intensity of contact 12310 or 12330 correspond totactile sensations that simulate an up-click.

While M and N have been discussed herein as positive integers, in somecircumstances M is zero (e.g., no activation states of the userinterface object are changed in response to detecting the increase inintensity of the contact) and/or N is zero (e.g., no activation statesof the user interface object are changed in response to detecting thedecrease in intensity of the contact). Additionally, while M has beendescribed as being different from N, in some circumstances M is equal toN (e.g., the number of activation states that are changed in response todetecting the increase in intensity of the contact is the same as thenumber of activation states that are changed in response to detectingthe decrease in intensity of the contact).

It should be understood that the particular order in which theoperations in FIGS. 12A-12B have been described is merely exemplary andis not intended to indicate that the described order is the only orderin which the operations could be performed. One of ordinary skill in theart would recognize various ways to reorder the operations describedherein. Additionally, it should be noted that details of other processesdescribed herein with respect to other methods described herein (e.g.,those listed in the fifth paragraph of the Description of Embodiments)are also applicable in an analogous manner to method 12400 describedabove with respect to FIGS. 12A-12B. For example, the contacts, userinterface objects, tactile outputs, intensity thresholds, focusselectors, and animations described above with reference to method 12400optionally has one or more of the characteristics of the contacts, userinterface objects, tactile outputs, intensity thresholds, focusselectors, and animations described herein with reference to othermethods described herein (e.g., those listed in the fifth paragraph ofthe Description of Embodiments). For brevity, these details are notrepeated here.

In accordance with some embodiments, FIG. 13 shows a functional blockdiagram of an electronic device 12500 configured in accordance with theprinciples of the various described embodiments. The functional blocksof the device are, optionally, implemented by hardware, software, or acombination of hardware and software to carry out the principles of thevarious described embodiments. It is understood by persons of skill inthe art that the functional blocks described in FIG. 13 are, optionally,combined or separated into sub-blocks to implement the principles of thevarious described embodiments. Therefore, the description hereinoptionally supports any possible combination or separation or furtherdefinition of the functional blocks described herein.

As shown in FIG. 13, an electronic device 12500 includes a display unit12502 configured to display a user interface object, where the userinterface object has a plurality of activation states; a touch-sensitivesurface unit 12504 configured to receive contacts; one or more sensorunits 12505 configured to detect intensity of contacts with thetouch-sensitive surface unit 12504; and a processing unit 12506 coupledto the display unit 12502, the touch-sensitive surface unit 12504, andthe sensor units 12505. In some embodiments, the processing unit 12506includes a detecting unit 12508, a changing unit 12510, a generatingunit 12512, and a display enabling unit 12514.

The processing unit 12506 is configured to: detect a contact on thetouch-sensitive surface unit 12504 (e.g., with the detecting unit12508); detect an increase of intensity of the contact on thetouch-sensitive surface unit 12504 from a first intensity to a secondintensity (e.g., with the detecting unit 12508); in response todetecting the increase in intensity: change activation states of theuser interface object M times, where M is a positive integer (e.g., withthe changing unit 12510), and generate a tactile output on thetouch-sensitive surface unit 12504 corresponding to each change inactivation state of the user interface object (e.g., with the generatingunit 12512); detect a decrease of intensity of the contact from thesecond intensity to the first intensity (e.g., with the detecting unit12508); and in response to detecting the decrease in intensity: changeactivation states of the user interface object N times, where N is apositive integer (e.g., with the changing unit 12510), and generate atactile output on the touch-sensitive surface unit 12504 correspondingto each change in activation state of the user interface object, where Nis different from M (e.g., with the generating unit 12512).

In some embodiments, the user interface object has a first appearance ina first activation state, the user interface object has a secondappearance, different from the first appearance, in a second activationstate, and the processing unit 12506 is configured to: in response todetecting the increase in intensity, enable display of an animation ofthe user interface object transitioning from the first appearance to thesecond appearance (e.g., with the display enabling unit 12514).

In some embodiments, M is greater than N.

In some embodiments, M is less than N.

In some embodiments, M is equal to 1 and N is equal to 2.

In some embodiments, M is equal to 2 and N is equal to 1.

In some embodiments, at least one tactile output generated (e.g., withthe generating unit 12512) in response to detecting the increase inintensity corresponds to a tactile sensation that simulates a down-clickof a physical actuator mechanism, and at least one tactile outputgenerated (e.g., with the generating unit 12512) in response todetecting the decrease in intensity corresponds to a tactile sensationthat simulates an up-click of a physical actuator mechanism.

The operations in the information processing methods described aboveare, optionally implemented by running one or more functional modules ininformation processing apparatus such as general purpose processors(e.g., as described above with respect to FIGS. 1A and 3) or applicationspecific chips.

The operations described above with reference to FIGS. 12A-12B are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.13. For example, detection operations 12404, 12406, 12416, changingoperations 12410, 12420, and generating operations 12412, 12422 are,optionally, implemented by event sorter 170, event recognizer 180, andevent handler 190. Event monitor 171 in event sorter 170 detects acontact on touch-sensitive display 112, and event dispatcher module 174delivers the event information to application 136-1. A respective eventrecognizer 180 of application 136-1 compares the event information torespective event definitions 186, and determines whether a first contactat a first location on the touch-sensitive surface corresponds to apredefined event or sub-event, such as selection of an object on a userinterface. When a respective predefined event or sub-event is detected,event recognizer 180 activates an event handler 190 associated with thedetection of the event or sub-event. Event handler 190 optionallyutilizes or calls data updater 176 or object updater 177 to update theapplication internal state 192. In some embodiments, event handler 190accesses a respective GUI updater 178 to update what is displayed by theapplication. Similarly, it would be clear to a person having ordinaryskill in the art how other processes can be implemented based on thecomponents depicted in FIGS. 1A-1B.

Providing Feedback for Changing Activation States of a User InterfaceObject

Many electronic devices have graphical user interfaces that include userinterface objects, such as buttons and switches. In some circumstances,a user activates a user interface object to perform an operation oradjust a parameter or property. In some devices, a tactile sensation is,in some circumstances, perceived by the user for corresponding physicalinputs, such as clicks of a physical actuator mechanism (e.g., a mousebutton) that activate a switch. To make a virtual button or switcheasier to use, the virtual object optionally mimics the behavior of thecorresponding physical object. For example, haptic sensations is, insome circumstances, felt when a virtual switch is operated, with thehaptic sensations mimicking the sensations of the corresponding physicalswitch, such as mimicking the clicks of a physical actuator mechanism(e.g., a mouse button) that activates the switch. But physical objects,such as real buttons and switches, provide, in some circumstances,excessive tactile feedback in some situations, and too little feedbackin others. In such situations, a virtual object that just mimickedsensations of the corresponding physical object would also provide toomuch (or too little) feedback. But a virtual object does not have to beprovided with haptic feedback that just mimics tactile sensations fromthe corresponding physical object. The embodiments described belowprovide tactile feedback that is not tied to actuations of a physicalactuator mechanism. For example, tactile sensations related toactivation state changes are, optionally, provided. When tactilesensations not tied to physical actuations are provided for, the usercan better discern the activation state of the virtual button withoutbeing distracted by too much or too little tactile feedback. If a userinterface object goes through two or more activation state changes inrapid succession, haptic feedback does not need to be provided for eachchange in activation state, whereas the corresponding physical objectwould provide more tactile feedback. Also, the number of times thathaptic feedback is provided as a contact increases in intensity does nothave to be the same as the number of times that haptic feedback isprovided as the contact decreases in intensity. This asymmetry in thenumber of times that haptic feedback is provided as a contact increasesin intensity or decreases in intensity is, in some embodiments,dependent on how rapidly the contact intensity changes, and, in otherembodiments, independent of how rapidly the contact intensity changes.This additional (or alternative) feedback enables the user to operatethe device more quickly and efficiently, thereby creating a moreefficient human-machine interface.

FIGS. 14A-14N illustrate exemplary user interfaces for providingfeedback for changing activation states of a user interface object inaccordance with some embodiments. The user interfaces in these figuresare used to illustrate the processes described below, including theprocesses in FIGS. 15A-15C. FIGS. 14A-14N include intensity diagramsthat show the current intensity of the contact on the touch-sensitivesurface relative to a plurality of intensity thresholds including alight press intensity threshold (e.g., “IT_(L)”) and a deep pressintensity threshold (e.g., “IT_(D)”). In some embodiments, operationssimilar to those described below with reference to “IT_(L)” and “IT_(D)”are performed with reference to different intensity thresholds.

FIG. 14A illustrates an example of a user interface that includes one ormore user interface objects. Image editor user interface 12600 isdisplayed on display 450 (e.g., display 340) of a device (e.g., device300). Image 12602 is displayed in image editor user interface 12600 forediting in accordance with user commands. One or more user interfaceobjects (for example, buttons, sliders, rocker switches) optionallyinclude control user interface objects such as rocker switches 12604 andstatus user interface objects such as value indicators 12606 displayedin image editor user interface 12600. The user interface objects inFIGS. 14A-14G are configured to enable a user to issue commands forediting image 12602. For example, one or more rocker switches 12604, formodifying respective parameters of image 12602, are displayed in imageeditor user interface 12600. Values representing respective parametersare, optionally displayed in respective value indicators 12606. Rockerswitch 12604-1 is, optionally, used to modify the brightness of image12602, for example, and the brightness level (for example, representedby integers, with 0 as the middle value between the upper and lowerbounds) is displayed in value indicator 12606-1. Cursor 12608 is alsodisplayed on user interface 12600. In some embodiments, cursor 12608 isa mouse pointer. Cursor 12608 is an example of a focus selector.

A respective rocker switch 12604 optionally has a “minus” portion forreducing the value of a parameter associated with the rocker switch,indicated by the minus sign, and a “plus” portion for increasing thevalue of a parameter associated with the rocker switch, indicated by aplus sign. A rocker switch 12604 is, optionally, activated when a focusselector (e.g., cursor 12608) is positioned over either portion of therocker switch and an intensity of a contact associated with the focusselector changes. In some embodiments, the corresponding value decreasesor increases depending on the portion over which the focus selector ispositioned. When the focus selector is positioned over the “minus”portion, the corresponding value decreases when the rocker switch isactivated. When the focus selector is positioned over the “plus”portion, the corresponding value increases when the rocker switch isactivated. In FIG. 14A, cursor 12608 is positioned over the “minus”portion of rocker switch 12604-1.

When rocker switch 12604-1 is not activated, rocker switch 12604-1 isdisplayed in a neutral position, as shown FIG. 14A. When rocker switch12604-1 is activated, rocker switch 12604-1 is displayed as if eitherthe “minus” portion (if cursor 12608 is positioned over the “minus”portion when rocker switch 12604-1 is activated, thus rocker switch12604-1 is activated to decrease the value) or the “plus” portion (ifcursor 12608 is positioned over the “plus” portion when rocker switch12604-1 is activated, thus rocker switch 12604-1 is activated toincrease the value) is depressed. For example, FIG. 14B shows the“minus” portion of rocker switch 12604-1 being depressed. In someembodiments, when rocker switch 12604-1 is activated, an animationshowing a transition of rocker switch 12604-1 from the neutral positionto either depressed position is, optionally, displayed; and when rockerswitch 12604-1 is deactivated, an animation showing a transition ofrocker switch 12604-1 from either depressed position to the neutralposition is, optionally, displayed.

FIG. 14A shows contact 12610 detected on touch-sensitive surface 451(e.g., touchpad 355) of the device at an intensity that is above acontact detection threshold (e.g., “IT₀”) and below a light pressintensity threshold (e.g., “IT_(L)”) for activating rocker switch12604-1. While contact 12610 continues to be detected on touch-sensitivesurface 451 and cursor 12608 is positioned over the “minus” portion ofrocker switch 12604-1, the intensity of contact 12610 is, in somecircumstances, increased to a light press intensity that is above thelight press intensity threshold (e.g., “IT_(L)”) for activating rockerswitch 12604-1, and the increase in intensity is detected, as shown inFIG. 14B. In response to the detection of the increase in intensity,rocker switch 12604-1 is activated and the brightness level in valueindicator 12606-1 decreases. The brightness of image 12602 changes inaccordance with the change in the brightness level. In some embodiments,the rate of change in the brightness level is a relatively slow rate(e.g., 1 brightness level per time step). In some embodiments, rockerswitch 12604-1 is animated to show the “minus” portion being depressed.The brightness level continues to decrease as long as the intensity ofcontact 12610 does not decrease below the light press intensitythreshold (e.g., “IT_(L)”).

The intensity of contact 12610 is, in some circumstances, increasedfurther. While contact 12610 continues to be detected on touch-sensitivesurface 451 and cursor 12608 is still positioned over the “minus”portion of rocker switch 12604-1, the device detects an increase inintensity of contact 12610 from the light press intensity (e.g., anintensity between IT_(L) and IT_(D)) to a second, higher intensity thatis above a deep press intensity threshold (e.g., “IT_(D)”). In responseto this increase in intensity, rocker switch 12604-1 changes to afurther activation state, as shown in FIG. 14C where the portion of therocker switch under focus selector 12608 is pushed “into” the display,and brightness level decreases at a “medium” rate that is faster (e.g.,5 brightness levels per time step) than the rate of change at the lightpress intensity, and the brightness of image 12602 changes in accordancewith the change in the brightness level, as shown in FIG. 14C.

The intensity of contact 12610 is, in some circumstances, increased evenfurther. While contact 12610 continues to be detected on touch-sensitivesurface 451 and cursor 12608 is still positioned over the “minus”portion of rocker switch 12604-1, the intensity of contact 12610 isincreased from the first deep press intensity (e.g., an intensity aboveIT_(D) shown in FIG. 14C) to a second deep press intensity (e.g., anintensity above IT_(D) shown in FIG. 14D) that is higher than the firstdeep press intensity. In response to this increase in intensity, rockerswitch 12604-1 changes to a further activation state, as shown in FIG.14D where the portion of the rocker switch under focus selector 12608 ispushed even further “into” the display than shown in FIG. 14C, andbrightness level decreases at a “fast” rate that is faster (e.g., 10brightness levels per time step) than the rate of change at the firstdeep press intensity, and the brightness of image 12602 changes inaccordance with the change in the brightness level, as shown in FIG.14D.

From the second deep press intensity, the intensity of contact 12610 is,in some circumstances, increased even further. Depending on theimplementation, the rate at which the brightness level changesoptionally does or does not change further in response to the detectionof the increase in intensity, as the rate of change at the second deeppress intensity is, optionally, a predefined lower-bound (orupper-bound, for a rate of change where the brightness level increases)rate of change.

The intensity of contact 12610 is, optionally, decreased from the seconddeep press intensity to the first deep press intensity (e.g., anintensity above IT_(D) but below the second deep press intensity). Whilecontact 12610 continues to be detected on touch-sensitive surface 451and cursor 12608 is still positioned over the “minus” portion of rockerswitch 12604-1, the device detects a decrease in intensity of contact12610 from the second deep press intensity to the first deep pressintensity, as shown in FIG. 14E. In response to this decrease inintensity, rocker switch 12604-1 continues to be activated, andbrightness level decreases at the rate that corresponds to the firstdeep press intensity (e.g., 5 brightness levels per time unit), and thebrightness of image 12602 changes in accordance with the change in thebrightness level, as shown in FIG. 14E.

The intensity of contact 12610 is, optionally, further decreased fromthe first deep press intensity to the light press intensity (e.g., anintensity between IT_(L) and IT_(D)). While contact 12610 continues tobe detected on touch-sensitive surface 451 and cursor 12608 is stillpositioned over the “minus” portion of rocker switch 12604-1, the devicedetects a decrease in the intensity of contact 12610 from the first deeppress intensity to the light press intensity, as shown in FIG. 14F. Inresponse to this decrease in intensity, rocker switch 12604-1 continuesto be activated, and brightness level decreases at the ratecorresponding to the light press intensity (e.g., 1 brightness level pertime unit), and the brightness of image 12602 changes in accordance withthe change in the brightness level, as shown in FIG. 14F.

The intensity of contact 12610 is, optionally, further decreased fromthe light press intensity (e.g., an intensity between IT_(L) and IT_(D))to an intensity below the light press intensity threshold (e.g.,“IT_(L)”). While contact 12610 continues to be detected ontouch-sensitive surface 451 and cursor 12608 is still positioned overthe “minus” portion of rocker switch 12604-1, the device detects adecrease in intensity of contact 12610 from the light press intensity toan intensity below the light press intensity threshold (e.g., “IT_(L)”),as shown in FIG. 14G. In response to detecting this decrease inintensity, rocker switch 12604-1 is deactivated, and the brightnesslevel stops decreasing, as shown in FIG. 14G. The brightness of image12602 stops changing in accordance with the brightness level ceasing todecrease.

A user interface object, such as rocker switch 12604-1, optionally hasmultiple activation states. For example, the activation states forrocker switch 12604-1 are the different rates at which the brightnesslevel changes. For example, when rocker switch 12604-1 is in a “neutralactivation state,” while the contact has an intensity below a lightpress intensity threshold (e.g., an intensity below IT_(L)), thebrightness level is not changing, as shown in FIG. 14A; when rockerswitch 12604-1 is in a “light press activation state,” while the contacthas the light press intensity (e.g., an intensity between IT_(L) andIT_(D)), the brightness level is changing at a slow rate, as shown inFIG. 14B; when rocker switch 12604-1 is in a “first deep pressactivation state,” while the contact has the first deep press intensity(e.g., an intensity above IT_(D)), the brightness level is changing at amedium rate, as shown in FIG. 14C; and when rocker switch 12604-1 is ina “second deep press activation state,” while the contact has the seconddeep press intensity (e.g., an intensity above IT_(D) that is above thefirst deep press intensity), the brightness level is changing at a fastrate, as shown in FIG. 14D. Alternatively, the activation states of arocker switch correspond to values of a parameter (e.g., a firstactivation state corresponds to 0, a second activation state correspondsto 1, a third activation state corresponds to 2, and so on).

When the intensity of contact 12610 changes, rocker switch 12604-1optionally changes from the activation state at the starting intensity(e.g., a neutral activation state, as shown in FIG. 14A) to theactivation state at the destination intensity (e.g., a second deep pressactivation state, as shown in FIG. 14D). For example, when the intensityof contact 12610 changes from an intensity below the light pressintensity threshold (e.g., “IT_(L)”) to the second deep press intensity(e.g., an intensity above IT_(D) that is above the first deep pressintensity), the activation state of rocker switch 12604-1 changes from arate of 0 brightness levels per time step to a rate of 10 brightnesslevels per time step. As another example, when the intensity of contact12610 changes from the second deep press intensity to the first deeppress intensity (e.g., as illustrated in FIGS. 14D-14E), the activationstate of rocker switch 12604-1 changes from a rate of 10 brightnesslevels per time step to 5 brightness levels per time step. Thus, thechanges in the rate of change for the brightness level, described abovewith reference to FIGS. 14A-14G, are changes in the activation state ofrocker switch 12604-1.

In some embodiments, from the activation state at the startingintensity, rocker switch 12604-1 optionally changes to zero or moreintermediate activation states on the way to changing to the activationstate at the destination intensity. For example, when the intensity ofcontact 12610 increases from below the light press intensity threshold(e.g., “IT_(L)”) to the second deep press intensity, from the activationstate at the intensity below the light press intensity threshold (e.g.,“IT_(L)”), rocker switch 12604-1 changes to the activation state at thelight press intensity (e.g., corresponding to the light press activationstate) and then to the activation state at the first deep pressintensity (e.g., corresponding to the first deep press activationstate), on the way to changing to the activation state at the seconddeep press intensity (e.g., the second deep press activation state). Theactivation states at the first and second intensities (e.g., the lightpress activation state and the first deep press activation state) arethe intermediate activation states between the activation state at theintensity below the light press intensity threshold (e.g., “IT_(L)”) andthe activation state at the second deep press intensity.

In some embodiments, the number of intermediate activation statesbetween a starting activation state and a destination activation statefor an increase in intensity is different than the number ofintermediate activation states between a starting activation state and adestination activation state for a decrease in intensity. For example,referring back to FIGS. 14A-14G described above, on the decrease inintensity of contact 12610 shown in FIGS. 14D-14G, on the way tochanging from the rate of change at the second deep press intensity tothe rate at the neutral activation state, rocker switch 12604-1optionally skips either or both of the rates at the light pressintensity (e.g., corresponding to the light press activation state) andat the first deep press intensity (e.g., corresponding to the first deeppress activation state), while those rates are not skipped on theincrease in intensity shown in FIGS. 14A-14D. In some other embodiments,the intermediate activation states are not skipped, but the transitionsto these states is, in some circumstances, not be noticeable to the userbecause of the speed of the increase or decrease in intensity leads totransitions between activation states in such quick succession that theuser will, in some circumstances, perceive the entire activation statesequence as merely a transition from the starting activation state tothe destination activation state. In some embodiments, the device ispre-configured to skip intermediate activations states on the increaseor decrease in intensity. In some other embodiments, intermediateactivation states are skipped if the intensity increases or decreases ata rate that exceeds a threshold (e.g., a rate corresponding totransitioning between the intensity below IT_(L) and the intensity aboveIT_(D) in less than 0.5, 0.25, 0.1, 0.05 seconds or some otherreasonable amount of time). In the latter case, the user has somecontrol over whether intermediate activations states are skipped, as theuser controls how fast the intensity increases or decreases.

In response to the increase in the intensity of contact 12610, one ormore distinct tactile outputs are, optionally, generated ontouch-sensitive surface 451. For example, as the intensity increasesfrom below the light press intensity threshold (e.g., “IT_(L)”) to thesecond deep press intensity, as described above with reference to FIGS.14A-14D, one or more distinct tactile outputs are, optionally, generatedon touch-sensitive surface 451. For convenience, the number of tactileoutputs generated in response to the detection of the increase inintensity is referred to below as the variable “M.”

In response to the decrease in the intensity of contact 12610, one ormore distinct tactile outputs are, optionally, generated ontouch-sensitive surface 451. For example, as the intensity decreasesfrom the second deep press intensity to an intensity below the lightpress intensity threshold (e.g., “IT_(L)”), as described above withreference to FIGS. 14D-14G, one or more distinct tactile outputs are,optionally, generated on touch-sensitive surface 451. For convenience,the number of distinct tactile outputs generated in response to thedetection of the decrease in intensity is referred to below as thevariable “N.” In some circumstances, M and N are the same and in somecircumstances, M and N are different—for example, the number of tactileoutputs generated in response to the detection of the decrease inintensity is, in some circumstances, the same as or different than thenumber of tactile outputs generated in response to the detection of theincrease in intensity.

For example, the M tactile outputs are, optionally, tactile outputsgenerated at increments of the brightness level or increments of thechange in brightness level as the brightness level changes in responseto the detection of the increase in the intensity of contact 12610. Forexample, a tactile output is, optionally, generated at each of the 10'sin the brightness level or at each 10th level from the starting level.Similarly, the N tactile outputs are, optionally, tactile outputsgenerated at increments of the brightness level or increments of thechange in brightness level as the brightness level changes in responseto the detection of the decrease in intensity of contact 12610. In thisexample, the tactile outputs are not necessarily generated in responseto transitions in activation state.

In some embodiments, the M or N tactile outputs are generated forchanges or transitions in activation state; the tactile outputs mark thechanges or transitions in activation state. For example, a tactileoutput is, optionally, generated at each change in the rate of change inthe brightness level as the intensity of contact 12610 increases (e.g.,each of the M tactile outputs correspond to respective changes inactivation state), and a tactile output is, optionally, generated ateach change in the rate of change in the brightness level as theintensity of contact 12610 decreases (e.g., each of the N tactileoutputs correspond to respective changes in activation state). In someembodiments, when a change or transition in activation state is skippedor not noticeable to the user (e.g., because the rate of increase ordecrease in the intensity of contact 12610 occurs faster than a rate ofchange threshold), generation of one or more corresponding tactilesensations is, optionally forgone (e.g., the one or more correspondingtactile sensations associated with corresponding changes in activationstate are not generated by the device even though the changes inactivation state occur).

In some embodiments, a tactile output varies depending on whether thetactile output was generated in response to an increase or a decrease inthe intensity of contact 12610. A tactile output generated in responseto detection of an increase in the intensity of contact 12610 is,optionally, different from a tactile output generated in response todetection of a decrease in the intensity of contact 12610. The tactileoutputs are, optionally, different in movement profile, amplitude, orboth. In some embodiments, a tactile output generated in response todetection of an increase in the intensity of contact 12610 correspondsto a tactile sensation that simulates a down-click (e.g.,press-and-hold) of a physical button (e.g., a mouse button), and atactile output generated in response to detection of a decrease in theintensity of contact 12610 corresponds to a tactile sensation thatsimulates an up-click (e.g., release from a press-and-hold) of thephysical button.

FIG. 14H-14N illustrate an example of the user interfaces describedabove, with reference to FIGS. 14A-14G, implemented on a device (e.g.,device 100) with a touch-sensitive display 112. FIG. 14H illustratesimage editor user interface 12628 displayed on touch-sensitive display112 of a device. Image 12622 is displayed in image editor user interface12628 for editing in accordance with user commands. One or more userinterface objects (for example, buttons, sliders, rocker switches)optionally include control user interface objects such as rockerswitches 12604 and status user interface objects such as valueindicators 12606 displayed in image editor user interface 12628. Theuser interface objects in FIG. 14H-14N are configured to enable a userto issue commands for editing image 12622. For example, one or morerocker switches 12624, for modifying respective parameters of image12622, are displayed in image editor user interface 12628. Valuesrepresenting respective parameters are, optionally, displayed inrespective value indicators 12626. Rocker switch 12624-1 is, optionally,used to modify the brightness of image 12622, for example, and thebrightness value (for example, represented by integers, with 0 as themiddle value between the upper and lower bounds) is displayed in valueindicator 12626-1.

A respective rocker switch 12624 optionally has a “minus” portion, forreducing the value of a parameter associated with the rocker switchindicated by the minus sign, and a “plus” portion for increasing thevalue of a parameter associated with the rocker switch, indicated by aplus sign. A rocker switch 12624 is, optionally, activated when acontact is positioned over either portion of the rocker switch and anintensity of a contact associated with the focus selector changes. Insome embodiments, the corresponding value decreases or increasesdepending on the portion over which the contact is positioned. When thecontact is positioned over the “minus” portion, the corresponding valuedecreases when the rocker switch is activated. When the contact ispositioned over the “plus” portion, the corresponding value increaseswhen the rocker switch is activated. In FIG. 14H, contact 12630 ispositioned over the “minus” portion of rocker switch 12624-1.

When rocker switch 12624-1 is not activated, rocker switch 12624-1 isdisplayed in a neutral position, as shown FIG. 14H. When rocker switch12624-1 is activated, rocker switch 12624-1 is displayed as if eitherthe “minus” portion (if contact 12630 is positioned over the “minus”portion when rocker switch 12624-1 is activated, thus rocker switch12624-1 is activated to decrease the value) or the “plus” portion (ifcontact 12630 is positioned over the “plus” portion when rocker switch12624-1 is activated, thus rocker switch 12624-1 is activated toincrease the value) is depressed. For example, FIG. 14I shows the“minus” portion of rocker switch 12624-1 being depressed. In someembodiments, when rocker switch 12624-1 is activated, an animationshowing a transition of rocker switch 12624-1 from the neutral positionto either depressed position is, optionally, displayed; and when rockerswitch 12624-1 is deactivated, an animation showing a transition ofrocker switch 12624-1 from either depressed position to the neutralposition is, optionally, displayed.

FIG. 14H shows contact 12630 detected on touch-sensitive display 112 atan intensity that is above a contact detection threshold (e.g., “IT₀”)and below a light press intensity threshold (e.g., “IT_(L)”) foractivating rocker switch 12624-1. While contact 12630 continues to bedetected on touch-sensitive display 112 over the “minus” portion ofrocker switch 12624-1, the intensity of contact 12630 is, in somecircumstances, increased to a light press intensity that is above thelight press intensity threshold (e.g., “IT_(L)”) for activating rockerswitch 12624-1, and the increase in intensity is detected, as shown inFIG. 14I. In response to the detection of the increase in intensity,rocker switch 12624-1 is activated and the brightness level in valueindicator 12626-1 decreases. The brightness of image 12622 changes inaccordance with the change in the brightness level. In some embodiments,the rate of change in the brightness level is a relatively slow rate(e.g., 1 brightness level per time step). In some embodiments, rockerswitch 12624-1 is animated to show the “minus” portion being depressed.The brightness level continues to decrease as long as the intensity ofcontact 12630 does not decrease below the light press intensitythreshold (e.g., “IT_(L)”).

The intensity of contact 12630 is, in some circumstances, increasedfurther. While contact 12630 continues to be detected on touch-sensitivedisplay 112 over the “minus” portion of rocker switch 12624-1, thedevice detects an increase in intensity of contact 12630 from the lightpress intensity (e.g., an intensity between IT_(L) and IT_(D)) to asecond, higher intensity that is above a deep press intensity threshold(e.g., “IT_(D)”). In response to this increase in intensity, rockerswitch 12624-1 changes to a further activation state, as shown in FIG.14J where the portion of the rocker switch under the focus selector(e.g., contact 12630) is pushed “into” the display, and brightness leveldecreases at a “medium” rate that is faster (e.g., 5 brightness levelsper time step) than the rate of change at the light press intensity, andthe brightness of image 12622 changes in accordance with the change inthe brightness level, as shown in FIG. 14J.

The intensity of contact 12630 is, in some circumstances, increased evenfurther. While contact 12630 continues to be detected on touch-sensitivedisplay 112 over the “minus” portion of rocker switch 12624-1, theintensity of contact 12630 is increased from the first deep pressintensity (e.g., an intensity above IT_(D) shown in FIG. 14J) to asecond deep press intensity (e.g., an intensity above IT_(D) shown inFIG. 14K) that is higher than the first deep press intensity. Inresponse to this increase in intensity, rocker switch 12624-1 changes toa further activation state, as shown in FIG. 14K where the portion ofthe rocker switch under contact 12630 is pushed even further “into” thedisplay than shown in FIG. 14J, and brightness level decreases at a“fast” rate that is faster (e.g., 10 brightness levels per time step)than the rate of change at the first deep press intensity, and thebrightness of image 12622 changes in accordance with the change in thebrightness level, as shown in FIG. 14K.

From the second deep press intensity, the intensity of contact 12630 is,in some circumstances, increased even further. Depending on theimplementation, the rate at which the brightness level changesoptionally do or do not change further in response to the detection ofthe increase in intensity, as the rate of change at the second deeppress intensity is, optionally, a predefined lower-bound (orupper-bound, for a rate of change where the value increases) rate ofchange.

The intensity of contact 12630 is, optionally, decreased from the seconddeep press intensity to the first deep press intensity (e.g., anintensity above IT_(D) but below the second deep press intensity). Whilecontact 12630 continues to be detected on touch-sensitive display 112over the “minus” portion of rocker switch 12624-1, the device detects adecrease in intensity of contact 12630 from the second deep pressintensity to the first deep press intensity, as shown in FIG. 14L. Inresponse to this decrease in intensity, rocker switch 12624-1 continuesto be activated, and brightness level decreases at the rate thatcorresponds to the first deep press intensity (e.g., 5 brightness levelsper time unit), and the brightness of image 12622 changes in accordancewith the change in the brightness level, as shown in FIG. 14L.

The intensity of contact 12630 is, optionally, further decreased fromthe first deep press intensity to the light press intensity (e.g., anintensity between IT_(L) and IT_(D)). While contact 12630 continues tobe detected on touch-sensitive display 112 over the “minus” portion ofrocker switch 12624-1, the device detects a decrease in the intensity ofcontact 12630 from the first deep press intensity to the light pressintensity, as shown in FIG. 14M. In response to this decrease inintensity, rocker switch 12624-1 continues to be activated, andbrightness level decreases at the rate corresponding to at the lightpress intensity (e.g., 1 brightness level per time unit), and thebrightness of image 12622 changes in accordance with the change in thebrightness level, as shown in FIG. 14M.

The intensity of contact 12630 is, optionally, further decreased fromthe light press intensity (e.g., an intensity between IT_(L) and IT_(D))to an intensity below the light press intensity threshold (e.g.,“IT_(L)”). While contact 12630 continues to be detected ontouch-sensitive display 112 over the “minus” portion of rocker switch12624-1, the device detects a decrease in intensity of contact 12630from the light press intensity to an intensity below the light pressintensity threshold (e.g., “IT_(L)”), as shown in FIG. 14N. In responseto detecting this decrease in intensity, rocker switch 12624-1 isdeactivated, and the brightness level stops decreasing, as shown in FIG.14N. The brightness of image 12622 stops changing in accordance with thebrightness level ceasing to decrease.

A user interface object, such as rocker switch 12624-1, optionally hasmultiple activation states. For example, the activation states forrocker switch 12624-1 are the different rates at which the brightnesslevel changes. For example, when rocker switch 12624-1 is in a “neutralactivation state,” while the contact has an intensity below a lightpress intensity threshold (e.g., an intensity below IT_(L)), thebrightness level is not changing, as shown in FIG. 14H; when rockerswitch 12624-1 is in a “light press activation state,” while the contacthas the light press intensity (e.g., an intensity between IT_(L) andIT_(D)), the brightness level is changing at a slow rate, as shown inFIG. 14I; when rocker switch 12624-1 is in a “first deep pressactivation state,” while the contact has the first deep press intensity(e.g., an intensity above IT_(D)), the brightness level is changing at amedium rate, as shown in FIG. 14J; and when rocker switch 12624-1 is ina “second deep press activation state,” while the contact has the seconddeep press intensity (e.g., an intensity above IT_(D) that is above thefirst deep press intensity), the brightness level is changing at a fastrate, as shown in FIG. 14K. Alternatively, the activation states of arocker switch correspond to values of a parameter (e.g., a firstactivation state corresponds to 0, a second activation state correspondsto 1, a third activation state corresponds to 2, and so on).

When the intensity of contact 12630 changes, rocker switch 12624-1optionally changes from the activation state at the starting intensity(e.g., a neutral activation state, as shown in FIG. 14H) to theactivation state at the destination intensity (e.g., a second deep pressactivation state, as shown in FIG. 14K). For example, when the intensityof contact 12630 changes from an intensity below the light pressintensity threshold (e.g., “IT_(L)”) to the second deep press intensity(e.g., an intensity above IT_(D) that is above the first deep pressintensity), the activation state of rocker switch 12624-1 changes from arate of 0 brightness levels per time step to a rate of 10 brightnesslevels per time step. As another example, when the intensity of contact12630 changes from the second deep press intensity to the first deeppress intensity (e.g., as illustrated in FIGS. 14K-14L), the activationstate of rocker switch 12624-1 changes from a rate of 10 brightnesslevels per time step to a rate of 5 brightness levels per time step.Thus, the changes in the rate of change for the brightness level,described above with reference to FIGS. 14H-14N, are changes in theactivation state of rocker switch 12624-1.

In some embodiments, from the activation state at the startingintensity, rocker switch 12624-1 optionally changes to zero or moreintermediate activation states on the way to changing to the activationstate at the destination intensity. For example, when the intensity ofcontact 12630 increases from below the light press intensity threshold(e.g., “IT_(L)”) to the second deep press intensity, from the activationstate at the intensity below the light press intensity threshold (e.g.,“IT_(L)”), rocker switch 12624-1 changes to the activation state at thelight press intensity (e.g., corresponding to the light press activationstate) and then to the activation state at the first deep pressintensity (e.g., corresponding to the first deep press activationstate), on the way to changing to the activation state at the seconddeep press intensity (e.g., the second deep press activation state). Theactivation states at the first and second intensities (e.g., the lightpress activation state and the first deep press activation state) arethe intermediate activation states between the activation state at theintensity below the light press intensity threshold (e.g., “IT_(L)”) andthe activation state at the second deep press intensity.

In some embodiments, the number of intermediate activation statesbetween a starting activation state and a destination activation statefor an increase in intensity is different than the number ofintermediate activation states between a starting activation state and adestination activation state for a decrease in intensity. For example,referring back to FIGS. 14H-14N described above, on the decrease inintensity of contact 12630 shown in FIGS. 14K-14N, on the way tochanging from the rate of change at the second deep press intensity tothe rate at the neutral activation state, rocker switch 12624-1optionally skips either or both of the rates at the light pressintensity (e.g., corresponding to the light press activation state) andat the first deep press intensity (e.g., corresponding to the first deeppress activation state), while those rates are not skipped on theincrease in intensity shown in FIGS. 14H-14K. In some other embodiments,the intermediate activation states are not skipped, but the transitionsto these states are, in some circumstances, not be noticeable to theuser because of the speed of the increase or decrease in intensity leadsto transitions between activation states in such quick succession thatthe user perceives, in some circumstances, the entire activation statesequence as merely a transition from the starting activation state tothe destination activation state. In some embodiments, the device ispre-configured to skip intermediate activations states on the increaseor decrease in intensity. In some other embodiments, intermediateactivation states are skipped if the intensity increases or decreases ata rate that exceeds a threshold (e.g., the intensity changes from belowthe light press intensity threshold to the second deep press intensityin less than a predefined amount of time such as 0.05 seconds). In thelatter case, the user has some control over whether intermediateactivations states are skipped, as the user controls how fast theintensity increases or decreases.

In response to the increase in the intensity of contact 12630, one ormore distinct tactile outputs are, optionally, generated ontouch-sensitive display 112. For example, as the intensity increasesfrom below the light press intensity threshold (e.g., “IT_(L)”) to thesecond deep press intensity, as described above with reference to FIGS.14H-14K, one or more distinct tactile outputs are, optionally, generatedon touch-sensitive display 112. For convenience, the number of tactileoutputs generated in response to the detection of the increase inintensity is referred to below as the variable “M.”

In response to the decrease in the intensity of contact 12630, one ormore distinct tactile outputs are, optionally, generated ontouch-sensitive display 112. For example, as the intensity decreasesfrom the second deep press intensity to an intensity below the lightpress intensity threshold (e.g., “IT_(L)”), as described above withreference to FIGS. 14K-14N, one or more distinct tactile outputs are,optionally, generated on touch-sensitive display 112. For convenience,the number of distinct tactile outputs generated in response to thedetection of the decrease in intensity is referred to below as thevariable “N.” In some circumstances, M and N are the same and in somecircumstances, M and N are different—for example, the number of tactileoutputs generated in response to the detection of the decrease inintensity is, optionally, the same as or different than the number oftactile outputs generated in response to the detection of the increasein intensity.

For example, the M tactile outputs are, optionally, tactile outputsgenerated at increments of the brightness level or increments of thechange in brightness level as the brightness level changes in responseto the detection of the increase in the intensity of contact 12630. Forexample, a tactile output is, optionally, generated at each of the 10'sin the brightness level or at each 10th level from the starting level.Similarly, the N tactile outputs are, optionally, tactile outputsgenerated at increments of the brightness level or increments of thechange in brightness level as the brightness level changes in responseto the detection of the decrease in intensity of contact 12630. In thisexample, the tactile outputs are not necessarily generated in responseto transitions in activation state.

In some embodiments, the M or N tactile outputs are generated forchanges or transitions in activation state; the tactile outputs mark thechanges or transitions in activation state. For example, a tactileoutput is, optionally, generated at each change in the rate of change inthe brightness level as the intensity of contact 12630 increases (e.g.,each of the M tactile outputs correspond to respective changes inactivation state), and a tactile output is, optionally, generated ateach change in the rate of change in the brightness level as theintensity of contact 12630 decreases (e.g., each of the N tactileoutputs correspond to respective changes in activation state). In someembodiments, when a change or transition in activation state is skippedor not noticeable to the user (e.g., because the rate of increase ordecrease in the intensity of contact 12630 occurs faster than a rate ofchange threshold), generation of one or more corresponding tactilesensations is, optionally, forgone (e.g., the one or more correspondingtactile sensations associated with corresponding changes in activationstate are not generated by the device even though the changes inactivation state occur).

In some embodiments, a tactile output varies depending on whether thetactile output was generated in response to an increase or a decrease inthe intensity of contact 12630. A tactile output generated in responseto detection of an increase in the intensity of contact 12630 is,optionally, different from a tactile output generated in response todetection of a decrease in the intensity of contact 12630. The tactileoutputs are, optionally, different in movement profile, amplitude, orboth. In some embodiments, a tactile output generated in response todetection of an increase in the intensity of contact 12630 correspondsto a tactile sensation that simulates a down-click (e.g.,press-and-hold) of a physical button (e.g., a mouse button), and atactile output generated in response to detection of a decrease in theintensity of contact 12630 corresponds to a tactile sensation thatsimulates an up-click (e.g., release from a press-and-hold) of thephysical button.

FIGS. 15A-15C are flow diagrams illustrating a method 12700 of providingfeedback for changing activation states of a user interface object inaccordance with some embodiments. The method 12700 is performed at anelectronic device (e.g., device 300, FIG. 3, or portable multifunctiondevice 100, FIG. 1A) with a display and a touch-sensitive surface. Insome embodiments, the display is a touch screen display and thetouch-sensitive surface is on the display. In some embodiments, thedisplay is separate from the touch-sensitive surface. Some operations inmethod 12700 are, optionally, combined and/or the order of someoperations is, optionally, changed.

As described below, the method 12700 provides an intuitive way toprovide feedback for change activation states of a user interfaceobject. The method reduces the cognitive burden on a user when changingactivation states of a user interface object, thereby creating a moreefficient human-machine interface. For battery-operated electronicdevices, enabling a user to change activation states of a user interfaceobject faster and more efficiently conserves power and increases thetime between battery charges.

The device displays (12702) a user interface object on the display,where the user interface object has a first activation state and asecond activation state. FIG. 14A, for example, shows rocker switches12604, for adjusting parameters of an image, displayed in image editoruser interface 12600. A respective rocker switch 12604 has at least twoactivation states (e.g., a neutral activation state, a light pressactivation state, a first deep press activation state and/or a seconddeep press activation state), which optionally include various rates ofchange in the parameter value. As another example, FIG. 14H shows rockerswitches 12624 displayed in image editor user interface 12628. Arespective rocker switch 12624 has at least two activation states, whichoptionally include various rates of change in the parameter value. Arespective rocker switch 12624 has at least two activation states (e.g.,a neutral activation state, a light press activation state, a first deeppress activation state and/or a second deep press activation state).

The device detects (12704) a contact (e.g., a finger contact) on thetouch-sensitive surface. As shown in FIG. 14A, for example, contact12610 is detected on touch-sensitive surface 451. Also, as shown in FIG.14H, contact 12630 is detected on touch-sensitive display 112.

The device detects (12706) an increase of intensity of the contact onthe touch-sensitive surface from a first intensity to a secondintensity. FIGS. 14A-14D show an increase in the intensity of contact12610 from an intensity below a light press intensity threshold (e.g.,“IT_(L)”) for activating rocker switch 12604-1, to an intensity above adeep press intensity threshold (e.g., “IT_(D)”) and higher thanadditional intensities (e.g., a light press intensity that is betweenIT_(L) and IT_(D)) that are also above the threshold. FIGS. 14H-14Kshows an increase in the intensity of contact 12630 from an intensitybelow a light press intensity threshold (e.g., “IT_(L)”) for activatingrocker switch 12624-1, to an intensity above a deep press intensitythreshold (e.g., “IT_(D)”) and higher than additional intensities thatare also above the threshold (e.g., a light press intensity that isbetween IT_(L) and IT_(D)).

In response to detecting the increase in intensity (12708), the devicechanges (12710) activation states of the user interface from the firstactivation state to the second activation state, and generates (12712) Mdistinct tactile outputs on the touch-sensitive surface, where M is apositive integer. For example, in FIG. 14A-14D or 14H-14K, in responseto the detection of the increase in intensity from below the light pressintensity threshold (e.g., “IT_(L)”) to an intensity above a deep pressintensity threshold (e.g., “IT_(D)”), the rate of change in brightnesslevel changes from zero, to a “fast” rate (e.g., 10 brightness levelsper time step). The activation state for rocker switch 12604-1 or12624-1 changes from the activation state corresponding to the zero rate(e.g., the neutral activation state), through zero or more intermediateactivation states (e.g., the light press activation state and/or thefirst deep press activation state), to the activation statecorresponding to the “fast” rate (e.g., the second deep press activationstate). In response to the detection of the increase in intensity, Mtactile outputs are, optionally, generated. The M tactile outputs are,optionally, generated at predefined increments of the brightness level(e.g., whenever the ones digit in the brightness level is 0) or atpredefined increments of the change in the brightness level (e.g., every10th increment from the starting brightness level), as the brightness ofthe image (e.g., 12602 or 12622) changes in accordance with the rate ofchange of brightness level corresponding to the current activation stateof rocker switch 12604-1 or 12624-1.

In some embodiments, the M distinct tactile outputs correspond tochanges in activation state of the user interface object (12714). The Mtactile sensations are, optionally, generated whenever the activationstate of rocker switch 12604-1 or 12624-1 (e.g., the rate of change forthe brightness level) changes.

In some embodiments, while detecting the increase in intensity of thecontact, the device determines (12716) a rate at which the intensity ofthe contact is increasing. In accordance with a determination that therate at which the intensity of the contact is increasing remains below apredefined threshold (e.g., a rate corresponding to transitioningbetween the first intensity and the second intensity in less than 0.5,0.25, 0.1, 0.05 seconds or some other reasonable amount of time), thedevice generates (12718) a distinct tactile output for each transitionbetween activation states that occurs in response to detecting theincrease in intensity of the contact. In accordance with a determinationthat the rate at which the intensity of the contact is increasingexceeds the predefined threshold (e.g., a rate corresponding totransitioning between the first intensity and the second intensity inless than 0.5, 0.25, 0.1, 0.05 seconds or some other reasonable amountof time), the device forgoes (12720) generation of at least one distincttactile output for a respective transition between activation statesthat occurs in response to detecting the increase in intensity of thecontact. For example, as the intensity of contact 12610 increases frombelow the light press intensity threshold (e.g., “IT_(L)”) to anintensity above a deep press intensity threshold (e.g., “IT_(D)”), asdepicted in FIGS. 14A-14D, a speed of the intensity increase is,optionally, determined. As another example, as the intensity of contact12630 increases from below the light press intensity threshold (e.g.,“IT_(L)”) to an intensity above a deep press intensity threshold (e.g.,“IT_(D)”), as depicted in FIGS. 14H-14K, a speed of the intensityincrease is, optionally, determined. If the speed of the intensityincrease is below the predefined threshold, a tactile output isgenerated for each transition between activation states along the way.If the speed of the intensity increase is above the predefinedthreshold, generation of one or more of the tactile outputs is,optionally, forgone, for example the tactile outputs corresponding totransitions between intermediate activation states (e.g., a transitionsbetween the light press activation state and the first deep pressactivation state).

The device detects (12722) a decrease of intensity of the contact fromthe second intensity to the first intensity. As shown in FIGS. 14D-14G,for example, a decrease in the intensity of contact 12610 from anintensity above a deep press intensity threshold (e.g., “IT_(D)”) to anintensity below the light press intensity threshold (e.g., “IT_(L)”) isdetected. As shown in FIGS. 14K-14N, for example, a decrease in theintensity of contact 12630 from an intensity above a deep pressintensity threshold (e.g., “IT_(D)”) to an intensity below the lightpress intensity threshold (e.g., “IT_(L)”) is detected.

In response to detecting the decrease in intensity (12724), the devicechanges (12726) activation states of the user interface object from thesecond activation state (e.g., the second deep press activation state)to the first activation state (e.g., the neutral activation state), andgenerates (12732) N distinct tactile outputs on the touch-sensitivesurface, where N is a positive integer and N is different from M. Forexample, in FIG. 14D-14G or 14K-14N, in response to the detection of thedecrease in intensity from an intensity above a deep press intensitythreshold (e.g., “IT_(D)”) to an intensity below the light pressintensity threshold (e.g., “IT_(L)”), the rate of change in brightnesslevel changes from the “fast” rate (e.g., 10 per time step) to zero. Theactivation state for rocker switch 12604-1 or 12624-1 changes from theactivation state corresponding to the “fast” rate, through zero or moreintermediate activation states (e.g., a first deep press activationstate and/or a light press activation state), to the activation statecorresponding to the zero rate. In response to the detection of thedecrease in intensity, N tactile outputs are, optionally, generated. TheN tactile outputs are, optionally, generated at predefined increments ofthe brightness level (e.g., whenever the ones digit in the brightnesslevel is 0), at predefined increments of the change in the brightnesslevel (e.g., every 10th increment from the starting level), or when thebrightness start level starts changing and stops changing, as thebrightness level changes in accordance with the rate of changecorresponding to the current activation state of rocker switch 12604-1or 12624-1. In some circumstances N is different from M (e.g., as thebrightness level has optionally changed less on the decrease inintensity, or the tactile outputs are, optionally, predefined to begenerated at different points than the increments in the level or in thechange in level). For example, when the increase in intensity of thecontact is below the predefined threshold and the decrease in intensityof the contact is above the predefined threshold (e.g., a ratecorresponding to transitioning between the first intensity and thesecond intensity in less than 0.5, 0.25, 0.1, 0.05 seconds or some otherreasonable amount of time), the device generates tactile outputscorresponding to each the transitions between the neutral activationstate, the light press activation state, the first deep press activationstate and the second deep press activation state when the intensity ofthe contact is increasing, but the device generates tactile outputs foronly a subset of these transitions (e.g., only the transition betweenthe second deep press activation state and the neutral activationstate).

In some embodiments, changing activation states of the user interfaceobject from the first activation state to the second activation stateincludes transitioning through a first number of intermediate activationstates between the first activation state and the second activationstate; and changing activation states of the user interface object fromthe second activation state to the first activation state includestransitioning through a second number of intermediate activation statesbetween the second activation state and the first activation state(12728). For example, in FIG. 14A-14D or 14H-14K, the transition fromthe neutral activation state to the second deep press activation stateincludes intermediate transitions to the light press activation stateand the first deep press activation state. In FIG. 14D-14G or 14K-14N,the transition from the second deep press activation state to theneutral activation state includes intermediate transitions to the firstdeep press activation state and the light press activation state.

In some embodiments, the first number of intermediate activation statesbetween the first activation state and the second activation state isdifferent from the second number of intermediate activation statesbetween the second activation state and the first activation state(12730). For example, the increase in intensity of contact 12610 or12630 is, in some circumstances, at a speed below the predefinedthreshold, and the decrease in intensity of contact 12610 or 12630 is,in some circumstances, above the predefined threshold, and as a resultthe intermediate activations states on the decrease in intensity areskipped (e.g., processing the transition between the first deep pressactivation state and the second deep press activation state shown inFIGS. 14C-14D and skipping the transition between the second deep pressactivation threshold to the first deep press activation shown in FIGS.14D-14E).

In some embodiments, the N distinct tactile outputs correspond tochanges in activation state of the user interface object (12734). The Ntactile sensations are, optionally, generated whenever the activationstate of rocker switch 12604-1 or 12624-1 (e.g., the rate of change forthe brightness level) changes.

In some embodiments, while detecting the decrease in intensity of thecontact, the device determines (12736) a rate at which intensity of thecontact is decreasing. In accordance with a determination that the rateat which the intensity of the contact is decreasing remains below apredefined threshold (e.g., a rate corresponding to transitioningbetween the first intensity and the second intensity in less than 0.5,0.25, 0.1, 0.05 seconds or some other reasonable amount of time), thedevice generates (12738) a distinct tactile output for each transitionbetween activation states that occurs in response to detecting thedecrease in intensity of the contact. In accordance with a determinationthat the rate at which the intensity of the contact is decreasingexceeds the predefined threshold, the device forgoes (12740) generationof at least one distinct tactile output for a respective transitionbetween activation states that occurs in response to detecting thedecrease in intensity of the contact. For example, as the intensity ofcontact 12610 or 12630 decreases from an intensity above a deep pressintensity threshold (e.g., “IT_(D)”) to an intensity below the lightpress intensity threshold (e.g., “IT_(L)”), as depicted in FIG. 14D-14Gor 14K-14N, respectively, a speed of the intensity decrease is,optionally, determined. In some embodiments, if the speed of theintensity decrease is below the predefined threshold, a tactile outputis generated for each transition between activation states along theway. If the speed of the intensity decrease is above the predefinedthreshold, generation of one or more of the tactile outputs is,optionally, forgone, for example the tactile outputs corresponding totransitions between intermediate activation states, such as the lightpress activation state and the first deep press activation stateillustrated in FIGS. 14B-14C.

In some embodiments, at least one tactile output generated in responseto detecting the increase in intensity of the contact (e.g., 12610 or12630) corresponds to a tactile sensation that simulates a down-click ofa physical actuator mechanism (e.g., a tactile sensation that simulatesthe physical “down-click sensation” generated by the mechanical buttonapparatus of a physical button when a user activates the physicalbutton), and at least one tactile output generated in response todetecting the decrease in intensity of the contact (e.g., 12610 or12630) corresponds to a tactile sensation that simulates an up-click ofa physical actuator mechanism (e.g., a tactile sensation that simulatesthe physical “up-click sensation” generated by the mechanical buttonapparatus of a physical button when a user activates the physicalbutton).

As used herein, a distinct tactile output is a tactile output that wasgenerated to provide feedback corresponding to a user interface event(e.g., a change in the activation state of the user interface object,such as activation of a button or other control). In some embodiments,the touch-sensitive surface is moved by an actuator in accordance with aseparate waveform for each user interface event. The waveforms fordifferent user interface events optionally overlap, but a waveform thatwas generated to provide a tactile feedback for a particular userinterface event (e.g., activation of a button or change in activationstate of a control such as a rocker switch) will still generate adistinct tactile output. As used herein, an activation state of a userinterface object corresponds to an operational state of an applicationon the electronic device, and changing activation states of the userinterface object changes operational states of the application. If theuser interface object is an adjustable control interface such as amulti-state button, rocker-switch or slider, the activation states ofthe button/switch/slider are typically displayed by changing the visualappearance of the adjustable control interface (e.g., as a change inshading of a button, a change in rotation of a rocker switch or a changein position of a slider). Additionally, when the activation state of thebutton/switch/slider is changed, operation of an application associatedwith the button/switch/slider is changed accordingly. For example, if arocker switch controls the brightness of an image, the activation statesof the rocker switch correspond to different brightness levels of theimage, and when the rocker switch changes from a first activation stateto a second activation state, the brightness of the image changes from afirst brightness level corresponding to the first activation state ofthe rocker switch to a second brightness level corresponding to thesecond activation state of the rocker switch. In some embodiments,activation states correspond to image property levels (e.g., hue,saturation, exposure, brightness, contrast), content navigation states(e.g., channel selection, forward navigation, backward navigation,frame-by-frame navigation), system property adjustments (e.g., volumecontrol, screen brightness, date/time settings), rates of change, andother adjustable properties.

While M and N have been discussed herein as positive integers, in somecircumstances M is zero (e.g., tactile outputs are generated in responseto detecting the increase in intensity of the contact) and/or N is zero(e.g., no tactile outputs are generated in response to detecting thedecrease in intensity of the contact). Additionally, while M has beendescribed as being different from N, in some circumstances M is equal toN (e.g., the number of tactile outputs that are generated in response todetecting the increase in intensity of the contact is the same as thenumber of tactile outputs that are generated in response to detectingthe decrease in intensity of the contact).

It should be understood that the particular order in which theoperations in FIGS. 15A-15C have been described is merely exemplary andis not intended to indicate that the described order is the only orderin which the operations could be performed. One of ordinary skill in theart would recognize various ways to reorder the operations describedherein. Additionally, it should be noted that details of other processesdescribed herein with respect to other methods described herein (e.g.,those listed in the fifth paragraph of the Description of Embodiments)are also applicable in an analogous manner to method 12700 describedabove with respect to FIGS. 15A-15C. For example, the contacts, userinterface objects, tactile outputs, intensity thresholds, focusselectors, animations described above with reference to method 12700optionally have one or more of the characteristics of the contacts, userinterface objects, tactile outputs, intensity thresholds, focusselectors, animations described herein with reference to other methodsdescribed herein (e.g., those listed in the fifth paragraph of theDescription of Embodiments). For brevity, these details are not repeatedhere.

In accordance with some embodiments, FIG. 16 shows a functional blockdiagram of an electronic device 12800 configured in accordance with theprinciples of the various described embodiments. The functional blocksof the device are, optionally, implemented by hardware, software, or acombination of hardware and software to carry out the principles of thevarious described embodiments. It is understood by persons of skill inthe art that the functional blocks described in FIG. 16 are, optionally,combined or separated into sub-blocks to implement the principles of thevarious described embodiments. Therefore, the description hereinoptionally supports any possible combination or separation or furtherdefinition of the functional blocks described herein.

As shown in FIG. 16, an electronic device 12800 includes a display unit12802 configured to display a user interface object, wherein the userinterface object has a first activation state and a second activationstate; a touch-sensitive surface unit 12804 configured to receivecontacts; one or more sensor units 12805 configured to detect intensityof contacts with the touch-sensitive surface unit 12804; and aprocessing unit 12806 coupled to the display unit 12802, thetouch-sensitive surface unit 12804 and the sensor units 12805. In someembodiments, the processing unit 12806 includes a detecting unit 12808,a changing unit 12810, a generating unit 12812, and a determining unit12814.

The processing unit 12806 is configured to: detect a contact on thetouch-sensitive surface unit 12804 (e.g., with the detecting unit12808); detect an increase of intensity of the contact on thetouch-sensitive surface unit 12804 from a first intensity to a secondintensity (e.g., with the detecting unit 12808); in response todetecting the increase in intensity: change activation states of theuser interface object from the first activation state to the secondactivation state (e.g., with the changing unit 12810); and generate Mdistinct tactile outputs on the touch-sensitive surface unit 12804,where M is a positive integer (e.g., with the generating unit 12812);detect a decrease of intensity of the contact from the second intensityto the first intensity (e.g., with the detecting unit 12808); and inresponse to detecting the decrease in intensity: change activationstates of the user interface object from the second activation state tothe first activation state (e.g., with the changing unit 12810); andgenerate N distinct tactile outputs on the touch-sensitive surface unit12804 (e.g., with the generating unit 12812), where N is a positiveinteger and N is different from M.

In some embodiments, changing activation states of the user interfaceobject from the first activation state to the second activation stateincludes transitioning through a first number of intermediate activationstates between the first activation state and the second activationstate; and changing activation states of the user interface object fromthe second activation state to the first activation state includestransitioning through a second number of intermediate activation statesbetween the second activation state and the first activation state.

In some embodiments, the first number of intermediate activation statesbetween the first activation state and the second activation state isdifferent from the second number of intermediate activation statesbetween the second activation state and the first activation state.

In some embodiments, the processing unit 12806 is configured to: whiledetecting the increase in intensity of the contact, determine a rate atwhich the intensity of the contact is increasing (e.g., with thedetermining unit 12814); in accordance with a determination that therate at which the intensity of the contact is increasing remains below apredefined threshold, generate a distinct tactile output for eachtransition between activation states that occurs in response todetecting the increase in intensity of the contact (e.g., with thegenerating unit 12812); and in accordance with a determination that therate at which the intensity of the contact is increasing exceeds thepredefined threshold, forgo generation of at least one distinct tactileoutput for a respective transition between activation states that occursin response to detecting the increase in intensity of the contact (e.g.,with the generating unit 12812).

In some embodiments, the processing unit 12806 is configured to: whiledetecting the decrease in intensity of the contact, determine a rate atwhich intensity of the contact is decreasing (e.g., with the determiningunit 12814); in accordance with a determination that the rate at whichthe intensity of the contact is decreasing remains below a predefinedthreshold, generate a distinct tactile output for each transitionbetween activation states that occurs in response to detecting thedecrease in intensity of the contact (e.g., with the generating unit12812); and in accordance with a determination that the rate at whichthe intensity of the contact is decreasing exceeds the predefinedthreshold, forgo generation of at least one distinct tactile output fora respective transition between activation states that occurs inresponse to detecting the decrease in intensity of the contact (e.g.,with the generating unit 12812).

In some embodiments, the M distinct tactile outputs correspond tochanges in activation state of the user interface object.

In some embodiments, the N distinct tactile outputs correspond tochanges in activation state of the user interface object.

In some embodiments, at least one tactile output generated in responseto detecting the increase in intensity corresponds to a tactilesensation that simulates a down-click of a physical actuator mechanism;and at least one tactile output generated in response to detecting thedecrease in intensity corresponds to a tactile sensation that simulatesan up-click of a physical actuator mechanism.

The operations in the information processing methods described aboveare, optionally implemented by running one or more functional modules ininformation processing apparatus such as general purpose processors(e.g., as described above with respect to FIGS. 1A and 3) or applicationspecific chips.

The operations described above with reference to FIGS. 15A-15C are,optionally, implemented by components depicted in FIG. 1A-1B or FIG. 16.For example, detection operations 12704, 12706, and 12722, changingoperations 12710 and 12726, and generating operations 12712 and 12732are, optionally, implemented by event sorter 170, event recognizer 180,and event handler 190. Event monitor 171 in event sorter 170 detects acontact on touch-sensitive display 112, and event dispatcher module 174delivers the event information to application 136-1. A respective eventrecognizer 180 of application 136-1 compares the event information torespective event definitions 186, and determines whether a first contactat a first location on the touch-sensitive surface corresponds to apredefined event or sub-event, such as selection of an object on a userinterface. When a respective predefined event or sub-event is detected,event recognizer 180 activates an event handler 190 associated with thedetection of the event or sub-event. Event handler 190 optionallyutilizes or calls data updater 176 or object updater 177 to update theapplication internal state 192. In some embodiments, event handler 190accesses a respective GUI updater 178 to update what is displayed by theapplication. Similarly, it would be clear to a person having ordinaryskill in the art how other processes can be implemented based on thecomponents depicted in FIGS. 1A-1B.

It should be understood that the particular order in which theoperations have been described above is merely exemplary and is notintended to indicate that the described order is the only order in whichthe operations could be performed. One of ordinary skill in the artwould recognize various ways to reorder the operations described herein.Additionally, it should be noted that the various processes separatelydescribed herein (e.g., those listed in the fifth paragraph of theDescription of Embodiments) can be combined with each other in differentarrangements. For example, the contacts, user interface objects, tactilesensations, intensity thresholds, and/or focus selectors described abovewith reference to any one of the various processes separately describedherein (e.g., those listed in the fifth paragraph of the Description ofEmbodiments) optionally have one or more of the characteristics of thecontacts, gestures, user interface objects, tactile sensations,intensity thresholds, and focus selectors described herein withreference to one or more of the other methods described herein (e.g.,those listed in the fifth paragraph of the Description of Embodiments).For brevity, all of the various possible combinations are notspecifically enumerated here, but it should be understood that theclaims described above may be combined in any way that is not precludedby mutually exclusive claim features.

The foregoing description, for purpose of explanation, has beendescribed with reference to specific embodiments. However, theillustrative discussions above are not intended to be exhaustive or tolimit the various described embodiments to the precise forms disclosed.Many modifications and variations are possible in view of the aboveteachings. The embodiments were chosen and described in order to bestexplain the principles of the various described embodiments and theirpractical applications, to thereby enable others skilled in the art tobest utilize the various described embodiments with variousmodifications as are suited to the particular use contemplated.

What is claimed is:
 1. A non-transitory computer readable storage mediumstoring one or more programs, the one or more programs comprisinginstructions, which when executed by an electronic device with adisplay, a touch-sensitive surface and one or more sensors to detectintensities of contacts with the touch-sensitive surface, cause thedevice to: display a user interface object on the display, wherein theuser interface object has a plurality of activation states, wherein theplurality of activation states includes a first activation state thatcorresponds to advancing through values at a first rate and a secondactivation state that corresponds to advancing through the values at asecond rate; detect a contact on the touch-sensitive surface; detect anincrease of intensity of the contact on the touch-sensitive surface froma first intensity to a second intensity; in response to detecting theincrease in intensity: change activation states of the user interfaceobject M times, where M is a positive integer, including advancingthrough the values at the first rate when the user interface object isin the first activation state and advancing through the values at thesecond rate when the user interface object is in the second activationstate; and generate a tactile output on the touch-sensitive surfacecorresponding to each change in activation state of the user interfaceobject, including generating a tactile output when the user interfaceobject transitions from the first activation state to the secondactivation state; detect a decrease of intensity of the contact from thesecond intensity to the first intensity; and in response to detectingthe decrease in intensity: change activation states of the userinterface object N times, where N is a positive integer, includingskipping changing to the second activation state of the user interfaceobject and skipping advancing through the values at the second rate inresponse to detecting the decrease in intensity; and generate a tactileoutput on the touch-sensitive surface corresponding to each change inactivation state of the user interface object, where N is different fromM, including forgoing generating a tactile output that corresponds totransitioning to and/or from the second activation state.
 2. Thenon-transitory computer readable storage medium of claim 1, wherein: theuser interface object has a first appearance in a first activationstate; the user interface object has a second appearance, different fromthe first appearance, in a second activation state; and thenon-transitory computer readable storage medium includes instructionswhich cause the device to, in response to detecting the increase inintensity, display an animation of the user interface objecttransitioning from the first appearance to the second appearance.
 3. Thenon-transitory computer readable storage medium of claim 1, wherein M isgreater than N.
 4. The non-transitory computer readable storage mediumof claim 1, wherein M is less than N.
 5. The non-transitory computerreadable storage medium of claim 1, wherein M is equal to 1 and N isequal to
 2. 6. The non-transitory computer readable storage medium ofclaim 1, wherein M is equal to 2 and N is equal to
 1. 7. Thenon-transitory computer readable storage medium of claim 1, wherein: atleast one tactile output generated in response to detecting the increasein intensity corresponds to a tactile sensation that simulates adown-click of a physical actuator mechanism; and at least one tactileoutput generated in response to detecting the decrease in intensitycorresponds to a tactile sensation that simulates an up-click of aphysical actuator mechanism.
 8. An electronic device, comprising: adisplay; a touch-sensitive surface; one or more sensors to detectintensities of contacts with the touch-sensitive surface; one or moreprocessors; memory; and one or more programs, wherein the one or moreprograms are stored in the memory and configured to be executed by theone or more processors, the one or more programs including instructionsfor: displaying a user interface object on the display, wherein the userinterface object has a plurality of activation states, wherein theplurality of activation states includes a first activation state thatcorresponds to advancing through values at a first rate and a secondactivation state that corresponds to advancing through the values at asecond rate; detecting a contact on the touch-sensitive surface;detecting an increase of intensity of the contact on the touch-sensitivesurface from a first intensity to a second intensity; in response todetecting the increase in intensity: changing activation states of theuser interface object M times, where M is a positive integer, includingadvancing through the values at the first rate when the user interfaceobject is in the first activation state and advancing through the valuesat the second rate when the user interface object is in the secondactivation state; and generating a tactile output on the touch-sensitivesurface corresponding to each change in activation state of the userinterface object, including generating a tactile output when the userinterface object transitions from the first activation state to thesecond activation state; detecting a decrease of intensity of thecontact from the second intensity to the first intensity; and inresponse to detecting the decrease in intensity: changing activationstates of the user interface object N times, where N is a positiveinteger, including skipping changing to the second activation state ofthe user interface object and skipping advancing through the values atthe second rate in response to detecting the decrease in intensity; andgenerating a tactile output on the touch-sensitive surface correspondingto each change in activation state of the user interface object, where Nis different from M, including forgoing generating a tactile output thatcorresponds to transitioning to and/or from the second activation state.9. The device of claim 8, wherein: the user interface object has a firstappearance in a first activation state; the user interface object has asecond appearance, different from the first appearance, in a secondactivation state; and the device includes instructions for, in responseto detecting the increase in intensity, displaying an animation of theuser interface object transitioning from the first appearance to thesecond appearance.
 10. The device of claim 8, wherein M is greater thanN.
 11. The device of claim 8, wherein M is less than N.
 12. The deviceof claim 8, wherein M is equal to 1 and N is equal to
 2. 13. The deviceof claim 8, wherein M is equal to 2 and N is equal to
 1. 14. The deviceof claim 8, wherein: at least one tactile output generated in responseto detecting the increase in intensity corresponds to a tactilesensation that simulates a down-click of a physical actuator mechanism;and at least one tactile output generated in response to detecting thedecrease in intensity corresponds to a tactile sensation that simulatesan up-click of a physical actuator mechanism.
 15. A method, comprising:at an electronic device with a touch-sensitive surface and a display,wherein the device includes one or more sensors to detect intensity ofcontacts with the touch-sensitive surface: displaying a user interfaceobject on the display, wherein the user interface object has a pluralityof activation states, wherein the plurality of activation statesincludes a first activation state that corresponds to advancing throughvalues at a first rate and a second activation state that corresponds toadvancing through the values at a second rate; detecting a contact onthe touch-sensitive surface; detecting an increase of intensity of thecontact on the touch-sensitive surface from a first intensity to asecond intensity; in response to detecting the increase in intensity:changing activation states of the user interface object M times, where Mis a positive integer, including advancing through the values at thefirst rate when the user interface object is in the first activationstate and advancing through the values at the second rate when the userinterface object is in the second activation state; and generating atactile output on the touch-sensitive surface corresponding to eachchange in activation state of the user interface object, includinggenerating a tactile output when the user interface object transitionsfrom the first activation state to the second activation state;detecting a decrease of intensity of the contact from the secondintensity to the first intensity; and in response to detecting thedecrease in intensity: changing activation states of the user interfaceobject N times, where N is a positive integer, including skippingchanging to the second activation state of the user interface object andskipping advancing through the values at the second rate in response todetecting the decrease in intensity; and generating a tactile output onthe touch-sensitive surface corresponding to each change in activationstate of the user interface object, where N is different from M,including forgoing generating a tactile output that corresponds totransitioning to and/or from the second activation state.
 16. The methodof claim 15, wherein: the user interface object has a first appearancein a first activation state; the user interface object has a secondappearance, different from the first appearance, in a second activationstate; and the method includes, in response to detecting the increase inintensity, displaying an animation of the user interface objecttransitioning from the first appearance to the second appearance. 17.The method of claim 15, wherein M is greater than N.
 18. The method ofclaim 15, herein M is less than N.
 19. The method of claim 15, wherein Mis equal to 1 and N is equal to
 2. 20. The method of claim 15, wherein Mis equal to 2 and N is equal to
 1. 21. The method of claim 15, wherein:at least one tactile output generated in response to detecting theincrease in intensity corresponds to a tactile sensation that simulatesa down-click of a physical actuator mechanism; and at least one tactileoutput generated in response to detecting the decrease in intensitycorresponds to a tactile sensation that simulates an up-click of aphysical actuator mechanism.